SDK directory structure
The PingAccess SDK directories, <PA_HOME>/sdk and <PA_HOME>/deploy, contain these files and directories.
Deploy directory
The <PA_HOME>/deploy directory is created as a location for all third-party JAR files. PingAccess does not automatically generate any contents for this directory, but any files you place in it are automatically migrated during an upgrade.
The contents of the <PA_HOME>/deploy directory are loaded by the run.sh or run.bat command.
SDK directory
The <PA_HOME>/sdk directory contains these files and directories.
| File/Directory | Description |
|---|---|
|
Contains an overview of the SDK contents. |
|
Contains an overview of the steps necessary to build and use the samples. |
|
Contains a Maven project with example plug-in implementations for rules showing a wide range of functionality. You can use these examples for developing your own implementations. |
|
Contains the details of the |
|
Contains a maven project with example plug-in implementations for site authenticators. Use these examples for developing your own implementations. |
|
Contains the details of the |
|
Contains a maven project with example plug-in implementations for identity mappings. Use these examples for developing your own implementations. |
|
Contains the details of the |
|
Contains a maven project with example plug-in implementations for load balancing strategies. Use these examples for developing your own implementations. |
|
Contains the details of the |
|
Contains a maven project with example plug-in implementations for the locale override service. Use these examples for developing your own implementations. |
|
Contains the details of the |
|
Contains the SDK Javadocs. To get started, open |