mirror/dex - dex - xhrpb gitea

98 Tags

52 MiB

Tree: 6ae11a1cfe

Author	SHA1	Message	Date
Stephan Renatus	291cd9e01c	regenerate protobuf code Signed-off-by: Stephan Renatus <srenatus@chef.io>	7 years ago
Eric Chiang	c5de6fa733	*: regenerate proto	8 years ago
Eric Chiang	ba1660ae1f	*: revendor and regenerate protobuf files	9 years ago
rithu john	d201e49248	api: adding a gRPC call for listing refresh tokens.	9 years ago
Eric Chiang	f4bbab5056	server/internal: generate protobuf types	9 years ago
Eric Chiang	f778b2d33b	server: update refresh tokens instead of deleting and creating another The server implements a strategy called "Refresh Token Rotation" to ensure refresh tokens can only be claimed once. ref: https://tools.ietf.org/html/rfc6819#section-5.2.2.3 Previously "refresh_token" values in token responses where just the ID of the internal refresh object. To implement rotation, when a client redeemed a refresh token, the object would be deleted, a new one created, and the new ID returned as the new "refresh_token". However, this means there was no consistent ID for refresh tokens internally, making things like foreign keys very hard to implement. This is problematic for revocation features like showing all the refresh tokens a user or client has out. This PR updates the "refresh_token" to be an encoded protobuf message, which holds the internal ID and a nonce. When a refresh token is used, the nonce is updated to prevent reuse, but the ID remains the same. Additionally it adds the timestamp of each token's last use.	9 years ago