BankID4Keycloak is an identity provider for Keycloak, giving it superpowers by adding support for Swedish BankID. Please note, in order to use this in production a valid BankID contract is required, for more information see this page.
BankID is a registered trademark of Finansiell ID Teknik BID AB. We are not affiliated with, endorsed or sponsored by Finansiell ID Teknik BID AB.
Keycloak is a registered trademark of RedHat Inc. We are not affiliated with, endorsed or sponsored by RedHat Inc.
Clone the repository, enter the target directory and run
mvn clean package
Running the command above will create a jar-file in the target directory.
Copy the jar file to the Keycloak deployments directory. For further information on how to deploy components in Keycloak please see this page.
cp target/bankid4keycloak-1.0.0-SNAPSHOT.jar <KEYCLOAK_HOME>/standalone/deployments/
In order to access the BankID API a client certificate and a truststore is required, both in PKCS12 format.
To use BankID in production a valid contract is required, please contact one of the banks acting as resellers for more information.
A certificate for the BankID test environment can be downloaded using the following page
The password for the PKCS12 container and the private key is: qwerty123
The CA Certificate is available in the PDF "BankID Relying Party Guidelines v3.2.22" and can also found on this page. See pages 13 and 14 of the PDF for production and test certificates.
example of how to create a PKCS12 truststore from a pem formated file
keytool -importcert -file apa.pem -alias "BankID Test CA" -trustcacerts -storetype pkcs12 -keystore truststore.p12
Start Keycloak and log in to the admin console.
Under the "Identity Providers" heading add the "BankID e-legitimation" identity provider.