How to write a Custom SAML SSO Assertion Signer for WSO2 Identity Server
This is the 3rd post I am writing to explain the use of extension points in WSO2 Identity Server. WSO2 Identity Server has so many such extension points which are easily configurable and arm the server with lot of flexibility. With this, we can support so many domain specific requirements with minimum efforts.
- Firstly I have shared the usage and steps of writing a custom user store manager.
- Secondly a custom claim handler which is also related with SAML SSO Response.
- Now this third post deals with writing a custom SAML SSO Assertion signer.
What we can customize?
- Credentials used to sign the SAML Assertion (The private key)
- Signing Algorithm
- This sample can be extended to customize how we sign the SAML Response and validate the signature as well.
How?
We have to write a class extending
- The class 'org.wso2.carbon.identity.sso.saml.builders.signature.DefaultSSOSigner' or
- The interface 'org.wso2.carbon.identity.sso.saml.builders.signature.SSOSigner'
Needs to override the following method in our case to customize how we sign the assertion,
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
@Override | |
public Assertion doSetSignature(Assertion assertion, String signatureAlgorithm, X509Credential cred) throws IdentityException { | |
try { | |
//override the credentials with our desired one | |
cred = getRequiredCredentials(); | |
Signature signature = (Signature) buildXMLObject(Signature.DEFAULT_ELEMENT_NAME); | |
signature.setSigningCredential(cred); | |
signature.setSignatureAlgorithm(signatureAlgorithm); | |
signature.setCanonicalizationAlgorithm(Canonicalizer.ALGO_ID_C14N_EXCL_OMIT_COMMENTS); | |
try { | |
KeyInfo keyInfo = (KeyInfo) buildXMLObject(KeyInfo.DEFAULT_ELEMENT_NAME); | |
X509Data data = (X509Data) buildXMLObject(X509Data.DEFAULT_ELEMENT_NAME); | |
X509Certificate cert = (X509Certificate) buildXMLObject(X509Certificate.DEFAULT_ELEMENT_NAME); | |
String value = org.apache.xml.security.utils.Base64.encode(cred | |
.getEntityCertificate().getEncoded()); | |
cert.setValue(value); | |
data.getX509Certificates().add(cert); | |
keyInfo.getX509Datas().add(data); | |
signature.setKeyInfo(keyInfo); | |
} catch (CertificateEncodingException e) { | |
throw new IdentityException("errorGettingCert"); | |
} | |
assertion.setSignature(signature); | |
List<Signature> signatureList = new ArrayList<Signature>(); | |
signatureList.add(signature); | |
// Marshall and Sign | |
MarshallerFactory marshallerFactory = org.opensaml.xml.Configuration | |
.getMarshallerFactory(); | |
Marshaller marshaller = marshallerFactory.getMarshaller(assertion); | |
marshaller.marshall(assertion); | |
org.apache.xml.security.Init.init(); | |
Signer.signObjects(signatureList); | |
return assertion; | |
} catch (Exception e) { | |
throw new IdentityException("Error while signing the SAML Response message.", e); | |
} | |
Finally we have to update the identity.xml() as below with the above custom class we write overriding the methods.
<SAMLSSOSigner>org.wso2.custom.sso.signer.CustomSSOSigner</SAMLSSOSigner>
and place the compiled package with the above class at 'IS_HOME/repository/components/lib'
Now if we restart the server and run the SAML SSO scenario, the SAML SSO Assertion will be signed in the way we defined at the custom class we wrote.
Here you can find a complete sample code to customize the assertion signing procedure.
Here you can find a complete sample code to customize the assertion signing procedure.
Hope this helps..
Cheers!