You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem statement
It should be possible to dynamically configure the CNAAS-NMS api and frontend application to be compatible with any OIDC provider. This could be Google, Authy, Facebook, Microsoft and/or SURFconext. Ususally this is done by feeding the application with a .well-known-endpoint that configures the auth(n|z) of your application.
Describe the solution you'd like
Implement the authlib library to configure the api: https://authlib.org/
The dynamic configuration should look something like this
Problem statement
It should be possible to dynamically configure the CNAAS-NMS api and frontend application to be compatible with any OIDC provider. This could be Google, Authy, Facebook, Microsoft and/or SURFconext. Ususally this is done by feeding the application with a .well-known-endpoint that configures the auth(n|z) of your application.
Describe the solution you'd like
Implement the authlib library to configure the api: https://authlib.org/
The dynamic configuration should look something like this
The Authlib library provides a mechanism to retrieve tokens and dynamically and download the verification certificates into the application.
The text was updated successfully, but these errors were encountered: