When an application is retrieving a credential from Conjur, the application authenticates to Follower A. Follower B receives the next request to retrieve the credential.
What happens next?
A.
The Coniur Token is stateless and Follower B is able to validate the Token and satisfy the request.
B.
The Coniur Token is stateful and Follower B is unable to validate the Token promptinq the application to re-authenticate.
C.
The Coryur Token is stateless and Follower B redirects the request to Follower A to satisfy the request.
D.
The Coniur Token is stateful and Follower B redirects the request to Follower A to satisfy the request.
This is the correct answer because the Conjur Token is a JSON Web Token (JWT) that is signed by the Conjur master and contains the identity and permissions of the application. The Conjur Token is stateless, meaning that it does not depend on any stored session or transaction information on the server side. Therefore, any Conjur follower can validate the Token by verifying the signature and the expiration time, and satisfy the request by retrieving the credential from the local database. This allows the Conjur followers to be horizontally scalable and load balanced, and to provide high availability and performance for the applications. This answer is based on the Conjur documentation1 and the Conjur training course2.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit