Describe the feature
As a user, I want to reduce number of SignIns so that the user experience is enhanced
Describe the problems your feature request solves
There are two OAuth2 security flows currently. One is for OAuth2 PKCE for react website and the other is for the traefik forward-auth that protects the backend workspaces.
The PKCE application also provides user access to GitLab. The dedicated GitLab is not used in workspace-only releases thus obviating the need for PKCE signIn.
The feature request is to remove PKCE signIn for workspace-only releases.
Describe the solution you'd like
The current implementation in React application have <PrivateRoute> react component. This protection is not needed for workspace releases.
Describe alternatives you've considered
Single OAuth2 application for both traefik forward-auth and react website. This application can be created as a OAuth2 server flow like the one currently being used for traefik forward-auth but with addition of scopes used for react website. But such a mashing of two different OAuth2 flows is not recommended practice.
Additional context
dedicated building of workspace-only react website is required before this feature can be implemented. Such a website will only have workspace page and no other pages, i.e., Library and DigitalTwins pages are removed.
Success Criterion
Describe the final result with the help of a checklist if needed.
Checklist:
Describe the feature
As a user, I want to reduce number of SignIns so that the user experience is enhanced
Describe the problems your feature request solves
There are two OAuth2 security flows currently. One is for OAuth2 PKCE for react website and the other is for the traefik forward-auth that protects the backend workspaces.
The PKCE application also provides user access to GitLab. The dedicated GitLab is not used in workspace-only releases thus obviating the need for PKCE signIn.
The feature request is to remove PKCE signIn for workspace-only releases.
Describe the solution you'd like
The current implementation in React application have
<PrivateRoute>react component. This protection is not needed for workspace releases.Describe alternatives you've considered
Single OAuth2 application for both traefik forward-auth and react website. This application can be created as a OAuth2 server flow like the one currently being used for traefik forward-auth but with addition of scopes used for react website. But such a mashing of two different OAuth2 flows is not recommended practice.
Additional context
dedicated building of workspace-only react website is required before this feature can be implemented. Such a website will only have workspace page and no other pages, i.e., Library and DigitalTwins pages are removed.
Success Criterion
Describe the final result with the help of a checklist if needed.
Checklist: