Difference between revisions of "MITREid Connect"
(→ldap-server-overlay/src/main/webapp/WEB-INF) |
|||
| Line 19: | Line 19: | ||
There are at least 3 XML configuration files you will need in this directory (they will supercede the versions in the core MITREid Connect build): | There are at least 3 XML configuration files you will need in this directory (they will supercede the versions in the core MITREid Connect build): | ||
| − | * data-context.xml - This defaults to an in-memory database which is impractical for any longterm deploy as each restart would wipe out any existing trusted partners. While you may be able to simply comment out/in the appropriate data storage, you may also need to configure that storage. | + | * ''data-context.xml'' - This defaults to an in-memory database which is impractical for any longterm deploy as each restart would wipe out any existing trusted partners. While you may be able to simply comment out/in the appropriate data storage, you may also need to configure that storage. |
| − | * server-config.xml - This provides some basic server config (name, logo, url, etc). | + | * ''server-config.xml'' - This provides some basic server config (name, logo, url, etc). |
| − | * user-context.xml - This file is where you would put configuration details related to user authentication and admin users, version that comes with the ldap overlay should include some basic LDAP config info. | + | * ''user-context.xml'' - This file is where you would put configuration details related to user authentication and admin users, version that comes with the ldap overlay should include some basic LDAP config info. |
==NIEF Attributes== | ==NIEF Attributes== | ||
Revision as of 18:54, 24 May 2018
Contents
About
This page is a brief introduction to deploying MITREid Connect with support for NIEF Attributes/Claims.
Deploying
Generally to deploy a customized (customization is pretty much always required outside of test deployments) MITREid Connect does require at a minimum some basic understanding of source control (specifically git), as well as some level of comfort writing Java source code and configuring a Maven project. The information we provide will be light on these details, but will hopefully make sense to anyone already comfortable with these concepts.
Sample Project
GTRI has found the best starting point for deploying MITREid Connect is their LDAP Overlay: https://github.com/mitreid-connect/ldap-openid-connect-server
Even if you are not authenticating against an existing LDAP/Active Directory, it may be a good example of how to use the overlay model for your deploy.
Customizing
Once you have created your own overlay project, you will need to spend sometime adding code to map attributes, add some configuration for your attribute sources, and make sure you enable appropriate data storage mechanisms for your chosen data storage methodology. For simplicity we will focus on the changes you would make to the the specific LDAP overlay example.
ldap-server-overlay/src/main/webapp/WEB-INF
There are at least 3 XML configuration files you will need in this directory (they will supercede the versions in the core MITREid Connect build):
- data-context.xml - This defaults to an in-memory database which is impractical for any longterm deploy as each restart would wipe out any existing trusted partners. While you may be able to simply comment out/in the appropriate data storage, you may also need to configure that storage.
- server-config.xml - This provides some basic server config (name, logo, url, etc).
- user-context.xml - This file is where you would put configuration details related to user authentication and admin users, version that comes with the ldap overlay should include some basic LDAP config info.
