Wednesday, December 16, 2015

How to access Shibboleth as SP built in variables in your Application?

Most of the variables created by the SP are controlled by you, and correspond to mapped attributes. A few are built into the SP and can't be renamed.

The applicationId property derived for the request.
The internal session key assigned to the session associated with the request.
The entityID of the IdP that authenticated the user associated with the request.
The ISO timestamp provided by the IdP indicating the time of authentication.
The AuthenticationMethod or <AuthnContextClassRef> value supplied by the IdP, if any.
The AuthenticationMethod or <AuthnContextClassRef> value supplied by the IdP, if any.

<AuthnContextDeclRef> value supplied by the IdP, if any.

We can access all these variable as header in JAVA application.


Friday, December 4, 2015

Attribute Authority, Command Line Interface (AACLI)

Today, I have encountered one interesting tool in Shibboleth IdP which will check the resolver, filters and also the metadata so that you can know exactly what will happen in any given situation without starting the IdP. J

As a developer, I would say it’s a great tool as you don’t have to restart your IdP again and again after every changes.

The name of the tool is (Attribute Authority, Command Line Interface) ACCLI which is located in the IDP_HOME/bin directory and is called or aacli.bat.

How it works?

Make sure, you have set IDP_HOME to your system environment variable.

To check what all attribute it will return for userId SysAdmin and Service Provider EntityId “”)

aacli.bat --configDir=C:\idp\conf\ --principal=SysAdmin --requester=

Please check here for detail information.

How TOPT Works: Generating OTPs Without Internet Connection

Introduction Have you ever wondered how authentication apps like RSA Authenticator generate One-Time Passwords (OTPs) without requiring an i...