Continuing the series for ADFS 4.0 on Server 2016.
The confidential flow relies on a client_id and a secret_key to authenticate the user.
The gist for the Postman collection is here.
You need to update your ADFS FQDN and the client_id and secret_key.
ADFS returns:
{
"access_token": "eyJ...ErQ",
"token_type": "bearer",
"expires_in": 3600,
"scope": "openid"
}
You can plug the access token into a JWT viewer.
Enjoy!
No comments:
Post a Comment