[
https://issues.apache.org/jira/browse/FEDIZ-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Wulff resolved FEDIZ-69.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.2.0
Assignee: Oliver Wulff
> Support starting IDP with jetty maven plugin
> --------------------------------------------
>
> Key: FEDIZ-69
> URL: https://issues.apache.org/jira/browse/FEDIZ-69
> Project: CXF-Fediz
> Issue Type: Improvement
> Components: IDP
> Affects Versions: 1.1.0, 1.2.0
> Reporter: Oliver Wulff
> Assignee: Oliver Wulff
> Priority: Minor
> Fix For: 1.2.0
>
>
> If you want to test the IDP, you have to build it with Maven and then deploy
> it to a pre-configured Tomcat instance with certificates etc. To reduce time
> in setting all that up, the jetty maven plugin can be used to deploy the idp
> and optionally the sts component.
> The IDP can be started with:
> {code}
> mvn -Pstandalone,realm-a,sts
> {code}
> If you test the REST/JPA layer, you don't have to start the sts as well
> (profile 'sts').
> If you test WS-Federation with the IDP, you must start the sts as well.
> The profile 'standalone' means to start jetty embedded. You can launch both
> profiles in two different shells (but you must not run 'clean') otherwise you
> remove the war, db files of the other IDP.
> The following properties are supported idp.https.port, idp.http.port
> Default port for profile 'realm-a': 9443, 9080
> Default port for profile 'realm-b': 12443, 12080
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
