Bunny cyber tech...

OpenID Connect Sample with Signature Verification ID tokens are used in OpenID Connect to sign in users into client apps. But how to validate them? Like identity cards, they contain a number of attributes or claims. These are protected with a digital signature, or message authentication code (MAC), to ensure the token’s integrity and authenticity. ID tokens carry the following claims: Subject  (sub) — identifier for the authenticated user Issuer  (iss) and  audience  (aud) — specify the IdP that created the ID token and who it is intended for (the client_id) Timestamps  - issue (iat) and expiration (exp) times Other attributes , such as authentication time, strength, a nonce, and selected user details can also be included. So, I'm going to discuss how to verify the signature of ID token with sample web application. This is an improved version of the previous app. When it comes to  validate an ID Token, an app wants to verify the signature of the token, as wel

/ OpenID Connect Sample Web App In this document, I'm trying to demonstrate OpenID Connect with a sample web application. Before doing this we need to have a good idea about OpenID Connect. So if you need to learn about OpenID Connect you can read my previous post. OpenID Connect Introduction... I'm using MiniOr ange as my O penID Connect provider. There are some steps to follow to setup the OIDC application with MiniOrange.  First, create an account on miniorange and sign in to the account. Then go to the miniOrange Administrator Console. Create an application by selecting Apps > Configure Apps. In the Application name type “OIDC”. Enter your client information(First_name,Last_name) and Save. Once you have configured the application. Please note down the clientID and client secret by going to Apps > View Apps then Select your Open Id application and click on “Edit”. Then add this redirection endpoint to the application.  Again go to the miniOrang

What is OpenID Connect?? OpenID Connect is a simple identity layer built on top of the OAuth 2.0 protocol, which allows clients to verify the identity of an end user based on the authentication performed by an authorization server or identity provider (IdP), as well as to obtain basic profile information about the end user in an interoperable and REST-like manner. OpenID Connect specifies a RESTful HTTP API, using JSON as a data format.  OpenID Connect is an increasingly common authentication protocol: when an app prompts you to authenticate using your Facebook or Google+ credentials, the app is probably using OpenID Connect. OpenID Connect allows a range of clients, including web-based, mobile, and JavaScript clients, to request and receive information about authenticating  sessions and end-users. OIDC main purpose is to authenticate user one login and allow access to multiple services which is also known a s SSO (Single Sign-On). OneLogin provides a custom connector optio