We recommend using a certified OpenId Connect client to interact with our OpenId Connect APIs.
The following code samples demonstrate how to use various OpenId Client libraries.
- Dotnet Core 2.0 - This project is based on the default Dotnet MVC template with no authentication added and then adapted to use OpenId Connect.
StackOverflow discussions about "[onelogin] oidc client"
Answered Jun 10 2017
OneLogin supports public key (RS256) encryption and you can find the public keys courtesy of the well.known endpoint OneLogin provides. Ex. https://t3stc0.onelogin.com/oidc/.well-known/openid … on the specifics, check out the OIDC spec. I also highly recommend making your code be able to respond to changing keys as these keys are subject to change (I believe Google changes theirs daily!) But any decent open source OIDC client should be able to do this for you. …
Answered Aug 11 2016
the redirect. You could programmatically redirect to a dummy page that requires authentication that then redirects via your client stack e.g. OWIN OIDC. Also, there is no standard for the cookies so … you don't get SSO across multiple IDP unless they are federated together. So if no federation and you login to Auth0, you will still have to login to OneLogin. …
Answered Jul 24 2017
creating client-ids/secrets with hard-coded (at creation time) scopes. If it's the former please take a look at the OIDC documentation for how to configure an application. https://developers.onelogin.com … /openid-connect At this time, each application instance has it's own, generated clientid & secret. Either way, you'll need to configure your application to accept the client id & secret that are generated in OneLogin. …