Project

General

Profile

Actions

Feature #103

closed
JA

OpenID Connect

Feature #103: OpenID Connect

Added by Josip Almasi almost 4 years ago. Updated almost 4 years ago.

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.


Related issues 1 (0 open1 closed)

Follows Feature #26: oauthClosedJosip Almasi01/31/202201/31/2022

Actions

JA Updated by Josip Almasi almost 4 years ago Actions #1

  • Subject changed from OpenID to OpenID Connect

JA Updated by Josip Almasi almost 4 years ago Actions #2

JA Updated by Josip Almasi almost 4 years ago Actions #3

JA Updated by Josip Almasi almost 4 years ago Actions #4

  • 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 Actions #5

  • 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

Also available in: PDF Atom