Actions
Feature #103
closed
JA
OpenID Connect
Feature #103:
OpenID Connect
Status:
Rejected
Priority:
Normal
Assignee:
-
Start date:
02/01/2022
Due date:
02/01/2022
% Done:
0%
Estimated time:
Description
instead of Oauth2. It's on top of oauth anyway but provides identity.
JA Updated by Josip Almasi almost 4 years ago
- Subject changed from OpenID to OpenID Connect
JA Updated by Josip Almasi almost 4 years ago
- Precedes Feature #26: oauth added
JA Updated by Josip Almasi almost 4 years ago
- Precedes deleted (Feature #26: oauth)
JA Updated by Josip Almasi almost 4 years ago
- Due date set to 02/01/2022
- Start date changed from 01/28/2022 to 02/01/2022
- Follows Feature #26: oauth added
JA Updated by Josip Almasi almost 4 years ago
- Status changed from New to Rejected
This is waaaay too complicated.
It is actually responsibility of the auth client (vrspace server) to encrypt and maintain tokens.
Lack of clear examples, lack of support in spring, 3rd party libraries unsupported or vulnerable.
Actions