network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 2 months |
| seen | Feb 28 at 2:22 | |
| stats | profile views | 1 |
CS undergraduate. Almost there.
|
Apr 25 |
awarded | Student |
|
Feb 26 |
answered | What can a hacker do with an IP address? |
|
Feb 24 |
comment |
OAuth: client credentials vs tokens For example, my facebook password never expires, but I don't feel any risk as long as I'm not making it public. Shouldn't clients be trusted that they will take good care of their credentials or not be trusted even with tokens? |
|
Feb 24 |
comment |
OAuth: client credentials vs tokens I kind of agree... except for "There would be no expiry and no scope limitation on any specific session." An access control matrix could be maintained on the resource server so that a resource would be shared to a client only if the resource owner accepts. There would be no expiring, but I don't really get why it should be expiring at all. ¿Could you elaborate more on why tokens are more scalable than client identification via client credentials? |
|
Feb 23 |
comment |
OAuth: client credentials vs tokens My guess is that needing tokens are the result of separating the authorization server from the resource server, but nobody does that. |
|
Feb 23 |
awarded | Editor |
|
Feb 23 |
revised |
OAuth: client credentials vs tokens fixed grammar |
|
Feb 23 |
asked | OAuth: client credentials vs tokens |
