Instead of using the sample data.zip
archive from the Java Integration Kit package (see Deploying the sample configuration archive), you can
configure PingFederate manually.
data.zip
file. Then you can refer to the sample configuration as you
create your own adapter instances and connections.The following tables list the required adapter settings for the Java sample applications.
Identity provider adapter instance settings
See the IdP Adapter screen of the identity provider adapter configuration.
Field Name | Value |
---|---|
Password |
Must be six characters long and contain at least:
Note:
The sample applications are preconfigured to use the following password:
|
Authentication Service | https://pf_host:pf_port/IdpSample/MainPage?cmd=sso |
Advanced Fields | |
Logout Service | https://pf_host:pf_port/IdpSample/MainPage?cmd=slo |
localhost
) and port accordingly (see Deploying the applications to separate servlet containers).Service provider adapter instance settings
See the Instance Configuration screen of the service provider adapter instance configuration.
Field Name | Value |
---|---|
Password |
Must be six characters long and contain at least:
Note:
The sample applications are preconfigured to use the following password:
|
Advanced Fields | |
Account Link Service (Optional) | https://pf_host:pf_port/SpSample/MainPage?cmd=accountlink |
Logout Service | https://pf_host:pf_port/SpSample/MainPage?cmd=slo |
Service provider default URLs
See the Default URLs screen of the service provider configuration.
Field | Value |
---|---|
For SSO URL | https://pf_host:pf_port/SpSample/MainPage/ |
For SLO URL | https://pf_host:pf_port/SpSample/MainPage/ |