-
Notifications
You must be signed in to change notification settings - Fork 2
Home
Welcome to the OpenID-Connect-Java-Spring-Server wiki!
After cloning you'll need to patch spring_security_oauth:
cd spring_security_oauth
git apply ../upstream-patch/secoauth_183.patch
The project's pom file is configured to run the maven-replacer plugin. This plugin looks for a file named local-values.conf at the root of the project directory (not inside the server package, directly at OpenID-Connect-Java-Spring-Server/). This file should look like the following:
DB_URL=jdbc:mysql://msql_url
DB_USER=user
DB_PASSWORD=password
OPENID_IDENTIFIER=openid_identifier
OPENID_ROOT=root
OPENID_ADMINS=bob
with the proper values for your deployment filled in. The project will fail to build if the file cannot be found.
Since this file contains sensitive information (and will vary from deployment to deployment) it should not be checked in.
The project uses JCE through BouncyCastle. Your system may be set up to handle this already, in which case no further action is needed.
If you run into javax.crypto.JceSecurity errors, do the following:
-
Add the BouncyCastle Provider to your JRE/JDK, per instructions at http://www.bouncycastle.org/wiki/display/JA1/Provider+Installation/
-
Download the "Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files" for your JRE version from http://www.oracle.com/technetwork/java/javase/downloads/index.html (scroll to the bottom of the page).
-
Install the new policy files per the README file included in the download. The download contains new versions of local_policy.jar and US_export_policy.jar. These files must be placed in your jre/lib/security folder(s - multiple on Windows), replacing the current files. If you wish to at some point revert back to your original policy files, store the original files elsewhere.
Init and update the project sub-modules:
git submodule init
git submodule update
You'll need (http://maven.apache.org/)mvn2 installed to build via:
mvn package