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
I have been working on some functionality for mockoidc that would enable it to run under Docker for testing with multiple services. The core functionality breaks down into the following:
an authorization service service implementation that demonstrates a basic (very basic) system (root requiring valid JWT to access, login endpoint with basic auth via HTTP Request FormPost, and OIDC integration hooks to interact with mockoidc)
a manager interface for managing the authorization service instance and mockoidc instance (start, stop, load config)
a manager command-line tool for running the manager inside of docker with a JSON configuration files to load from (may be future take some settings from a HTTP request body for the commands)
the parts also expose a basic unauthenticated ping endpoint for system health
a client command-line tool for showing how to interact with it (take issuer URL and show the Well-Known OIDC Config; start/stop services, load config, access ping)
NOTE: I did need to expose the discoveryResponse type to DRY it and make sure the client saw the same thing.
This would effectively demonstrate #52 and likely #53 in the process, and make this project useful to those wanting to proof their JWT auth methodology in a Dockerized environment.
Any feedback would be appreciated. Looking to contribute this work at some point here in the future.
The text was updated successfully, but these errors were encountered:
I have been working on some functionality for
mockoidc
that would enable it to run under Docker for testing with multiple services. The core functionality breaks down into the following:authorization service
service implementation that demonstrates a basic (very basic) system (root requiring valid JWT to access, login endpoint with basic auth via HTTP Request FormPost, and OIDC integration hooks to interact withmockoidc
)mockoidc
instance (start, stop, load config)ping
endpoint for system healthNOTE: I did need to expose the
discoveryResponse
type to DRY it and make sure the client saw the same thing.This would effectively demonstrate #52 and likely #53 in the process, and make this project useful to those wanting to proof their JWT auth methodology in a Dockerized environment.
Any feedback would be appreciated. Looking to contribute this work at some point here in the future.
The text was updated successfully, but these errors were encountered: