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

Added a couple phrases and formatting.

master
aanganes 2013-04-26 10:48:03 -07:00
parent f861e126dd
commit 39a3341275
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Build-Instructions.md

@ -15,7 +15,7 @@ The project has a hierarchical layout:
+-- openid-connect-client
+-- openid-connect-server
The root of the project contains a `pom.xml` file that references all sub-modules and manages dependencies for the entire project.
`openid-connect-common`, `openid-connect-client`, and `openid-connect-server` are each managed as individual Maven submodules. The root of the project contains a `pom.xml` file that references all sub-modules and manages dependencies for the entire project.
# Building with Maven
@ -23,9 +23,9 @@ The project uses the Maven `package` directive to build from the root of the pro
`mvn package`
By building in the root, Maven automatically builds all dependencies across. Building directly in the submodules will often fail as the cross-dependencies on other portions of the project (such as the server's dependency on common) will not have been built yet.
By building in the root, Maven automatically builds all dependencies across submodules. Building directly in the submodules will often fail as the cross-dependencies on other portions of the project (such as the server's dependency on common) will not have been built yet.
The build process produces a .jar file for openid-connect-common and openid-connect-client and a .war file for openid-connect-server in the following directories:
The build process produces a .jar file for `openid-connect-common` and `openid-connect-client` and a .war file for `openid-connect-server` in the following directories:
openid-connect-client/target/openid-connect-client-{VERSION}.jar
openid-connect-common/target/openid-connect-common-{VERSION}.jar
@ -51,7 +51,7 @@ To configure an http and https proxy, add this option (especially because Maven
The server is configured out of the box to use an in-memory HyperSQL database (hsqldb). All data that the server stores, such as tokens, clients, and user authorizations, will be lost when the server is shut down. In order to persist data for longer than a single session, it is necessary to change the data source as configured in `openid-connect-server/src/main/webapp/WEB-INF/data-context.xml`.
The server is auto-configured with one client and four users, which are enumerated in the file `openid-connect-server/src/main/resources/db/clients.sql` and `openid-connect-server/src/main/resources/db/users.sql`. These files are automatically loaded by the hsqldb data source and can be augmented with other clients and users.
The server is auto-configured with one client and four users, which are enumerated in the file `openid-connect-server/src/main/resources/db/clients.sql` and `openid-connect-server/src/main/resources/db/users.sql`. These files are automatically loaded by the hsqldb data source and can be edited to hold other clients and users.
## Java Cryptographic Extensions (JCE)