NB-Public
/
keycloak-2fa-sms-authenticator
mirror of https://github.com/netzbegruenung/keycloak-2fa-sms-authenticator.git
0
0
Fork 0
Code Issues Projects Releases Wiki Activity
241 Commits 9 Branches 49 Tags 1.2 MiB
Java 89.7%
Fluent 6.1%
JavaScript 4.2%
Go to file
Sven Seeberg e8b58bf95c
Merge pull request #76 from netzbegruenung/bump-24.0.5 
Bump version to 24.0.5
 		2024-04-23 14:40:40 +02:00
.github Replace unmaintained automatic release action 2024-03-27 08:33:21 +01:00
app-authenticator Bump version 24.0.3 2024-03-27 15:22:08 +01:00
app-authenticator-cli App authenticator docs and cli client (#66) 2024-03-27 08:33:14 +01:00
dev Bump version 24.0.3 2024-03-27 15:22:08 +01:00
docs Enhance enforce MFA documentation 2024-04-09 17:05:46 +02:00
enforce-mfa Add TOTP App name in selection dialog 2024-04-23 14:32:30 +02:00
sms-authenticator Bump version 24.0.3 2024-03-27 15:22:08 +01:00
.editorconfig Add challenge API tests 2024-03-27 08:32:58 +01:00
.gitignore Add clientName and clientUrl to challenge 2024-03-27 08:33:12 +01:00
CHANGELOG.md Bump v0.2.0 2022-07-15 09:30:39 +02:00
LICENSE Fix LICENSE headers & indentation 2022-06-26 10:20:52 +02:00
README.md Enhance enforce MFA documentation 2024-04-09 17:05:46 +02:00
pom.xml Bump version to 24.0.5 2024-04-23 14:38:37 +02:00

README.md

Keycloak MFA Plugin collection

This repository contains the source code for a collection of Keycloak MFA plugins. The plugins are:

  • SMS authenticator (production ready)
  • Force MFA & Selection dialog (work in progress)
  • Native App MFA integration (work in progress)

The different plugins are documented in the submodules README or in docs folder.

License

The code of this project is Apache 2.0 licensed. Parts of the original code are MIT licensed.

Development

Building

  1. Clone this repository
  2. Install Apache Maven
  3. Change into the cloned directory and run 
    mvn clean install
    A file target/netzbegruenung.keycloak-2fa-sms-authenticator.jar should be created.

If building fails and the problem is caused or related to the dev module or tests, try to run mvn clean install -DskipTests.

Releases

Deployment is done by github actions: .github/workflows/release.yml To trigger the release workflow be sure to have proper access rights and follow the steps below. https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules#about-tag-protection-rules

  1. Update project and submodules version mvn versions:set -DnewVersion=1.2.3; mvn versions:commit
  2. Commit your changes
  3. Add tag to your commit git tag -a v1.2.3 -m "Bump version 1.2.3"
  4. Trigger the release by git push --tags

After building completes the new release is available on github containing the jar files for each module.