github
/
OpenID-Connect-Java-Spring-Server
mirror of https://github.com/mitreid-connect/OpenID-Connect-Java-Spring-Server
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
2,740 Commits
17 Branches
69 Tags
78 MiB
Java 57.5%
JavaScript 32.3%
HTML 5.1%
Less 4.5%
PLSQL 0.4%
Other 0.2%
 
 
 
 
 
 
Go to file
semantic-release-bot b2b8efe516 chore(release): 3.0.1 [skip ci] 
## [3.0.1](https://github.com/CESNET/OpenID-Connect-Java-Spring-Server/compare/v3.0.0...v3.0.1) (2021-11-05)

### Bug Fixes

* 🐛 fix loading JWKS ([371adc1](371adc13fb))
 		2021-11-05 10:40:38 +00:00
.github/workflows chore: 🤖 Prepare for semantic release 2021-10-24 16:51:29 +02:00
perun-oidc-server chore(release): 3.0.1 [skip ci] 2021-11-05 10:40:38 +00:00
perun-oidc-server-webapp chore(release): 3.0.1 [skip ci] 2021-11-05 10:40:38 +00:00
.editorconfig Add Editorconfig for minimal code style support 2016-07-05 15:09:09 -04:00
.gitignore cleanup 2017-03-20 13:45:55 -04:00
.releaserc chore: fixed naming of .releaserc 2021-11-05 11:33:32 +01:00
.travis.yml refactoring submodule common - part 1 2021-08-12 11:00:54 +02:00
CHANGELOG.md chore(release): 3.0.1 [skip ci] 2021-11-05 10:40:38 +00:00
LICENSE.txt new year 2018 2018-02-12 10:39:04 -05:00
README.md chore: 🤖 Prepare for semantic release 2021-10-24 16:51:29 +02:00
README_zh_CN.md new year 2018 2018-02-12 10:39:04 -05:00
checkstyle.xml new year 2018 2018-02-12 10:39:04 -05:00
package.json chore: 🤖 Prepare for semantic release 2021-10-24 16:51:29 +02:00
pom.xml chore(release): 3.0.1 [skip ci] 2021-11-05 10:40:38 +00:00

README.md

MITREid Connect

This project has been forked from the MITREid Connect repository. However, due to split between the paths we want to take with the project, we have decided to remove the fork relationship. All the original code will stay licensed to the original project. We would like to thank the developers of the original project for their work and wish them all the best in its continuation.

Contribution

This repository uses Conventional Commits. Any change that significantly changes behavior in a backward-incompatible way or requires a configuration change must be marked as BREAKING CHANGE.