Skip to content

santesem-links/spid-saml-check-1

 
 

Repository files navigation

Per le istruzioni in Italiano, cliccare qui.

SPID SAML Check

SPID SAML Check is an application suite that provider some tools for Service Providers, useful for inspecting requests shipped to an Identity Provider, checking metadata compliance and sending custom responses back to Service Provider. It includes:

  • spid-sp-test to check the SPID specifications compliance
  • a web application (spid-validator) that provides an easy to use interface
  • a web application (spid-demo) that acts as a test IdP for demo purpose
  • an extension for Google Chrome that intercepts the request (deprecated)

SPID SAML Check has been developed and is maintained by AgID - Agenzia per l'Italia Digitale

How to build with Docker

git clone https://github.com/italia/spid-saml-check.git
cd spid-saml-check
docker build -t spid-saml-check .

How to run with Docker

docker run -t -i -p 8080:8080 spid-saml-check

How to use it as a SPID Validator

The application spid-validator, if invoked as a web application as is, provides "basic", formal validation of a Service Provider's SAML metadata.

In order to unleash the full set of SPID compliance tests (the proper SPID Validator), retrieve the metadata of SPID Validator at https://localhost:8080/metadata.xml and configure it on as a new Identity Provider (IdP) under your Service Provider (SP) implementation.

When used in this fashion, the SPID Validator can be invoked as an IdP from your SP, listing 300+ individual controls, divided into 7 families:

  • 4 families for the formal validation of the SP metadata (already described);
  • 3 families for the formal validation of the SP's SAML request;
  • 1 family (111 controls) for interactively validating the SP behaviour to SAML responses from IdP's.

To use the SPID Validator the AuthnRequest are thus sent from your SP, loggin in to Validator with credentials validator / validator

Usage steps

  • Copy spid-validator metadata to the SP you want to test with. spid-validator can be downloaded at: https://localhost:8080/metadata.xml

    wget https://localhost:8080/metadata.xml -O /path/to/your/sp/metadata/folder/spid-saml-check-metadata.xml
    
  • Start authentication request connecting to your SP, the AuthnRequest would be created and sent to spid-saml-check. You should access to a page like shown in the following picture

    login page
  • Submit validator / validator as credential

  • You would see the SAML2 Authn Request made from your SP

    authn request page
  • Click on Metadata -> Download and submit your SP metadata url.
    Warning: If your SP is on your localhost, please use your host Docker IP and not "localhost"!

    metadata download page
  • Now you'll be able to execute all the tests, in order of appareance: Metadata, Request and Response.

  • To check a Response, from Response section, select in the scroll menu the test you want to execute, then mark it as done and if successful

    response select page

How to use it as a SPID Demo

The application spid-demo runs at: https://localhost:8080/demo

demo index page

Test users of spid-demo that can be used are listed at: https://localhost:8080/demo/users

demo users page

Usage steps

  • Copy spid-demo metadata to the SP you want to test with. spid-demo metadata can be downloaded at: https://localhost:8080/demo/metadata.xml

    wget https://localhost:8080/demo/metadata.xml -O /path/to/your/sp/metadata/folder/spid-demo.xml
    
  • Go to https://localhost:8080 to register metadata of your SP on spid-validator. You should access to a page like shown in the following picture

    login page
  • Submit validator/ validator as credential

  • Click on Metadata -> Download and submit your SP metadata url.
    Warning: If your SP is on your localhost, please use your host Docker IP and not "localhost"!

    download metadata page
  • Send an authn request to spid-demo in order to use Demo environment

    demo idp

About

Tool di verifica implementazione SPID SAML

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • JavaScript 67.2%
  • SCSS 16.6%
  • CSS 6.5%
  • Handlebars 6.5%
  • HTML 2.8%
  • Dockerfile 0.4%