Hi Steffi, > In OAuth, the expires_in field is usually used to inform the client how long > the access token is valid. If the client uses the access token in a request > after the token expired, the RS will reject the request, which usually is not > a big problem for the client.
> In ACE, AS provides the client with keying material for the RS, which is a > completely different situation. If the client does not know how long the > keying material is valid, it may use outdated keying material to communicate > with RS. The expires_in field can be used to inform the client how long the > keying material for RS is valid, if the keying material is valid as long as > the access token. > The main reason to change keying material from time to time is to avoid that > it is compromised. I therefore think that it is necessary for the security of > the solution that C knows how long the keying material is supposed to be > valid. If a client uses either an old key or an old token then the request will fail. I don't see much difference here between OAuth and ACE. Adding a note to recommend the use of the expires_in field appears still useful to me. Ciao Hannes IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. _______________________________________________ Ace mailing list Ace@ietf.org https://www.ietf.org/mailman/listinfo/ace
