-
Notifications
You must be signed in to change notification settings - Fork 10
Open
Description
The OpenID Connect workflow provided in now included "cwbi-auth-http-client" is not, or at least doesn't have to be, specific to CWBI.
OpenID Connect, being a well defined started we should not assume at this level what OIDC provider is being used.
For some more clarity of intent: I should be able to "steal" this code for an OpenDCS thick client to connect to an Opendcs/rest_api instance hooked up to the Authelia OIDC provider in my HomeLab which could also be doing mTLS with it's own trust store. Which upon cursory review appears to reasonable except for a few hard coded strings from the initial push of development.
Metadata
Metadata
Assignees
Labels
No labels