Micro Focus Contributor
Micro Focus Contributor

HP PPM Integration with Remedy


I need to know if is it possible integrate PPM 9.32 with BMC Remedy 16.07-02.

If the answer is yes, how can we do? With a WebService? Could you attach some documentation about this?

We have a PPM installation in SaaS with SSO configured. The customer wants to use PPM RESTful services to implement some functionalities. Our problem is that we have never configured PPM RESTful services to access PPM via SSO. The PPM RESTful official document doesn’t provide any information about this.
We have found the information below, but I think is only applicable for SOAP webservices.
Any of you have any experience on this? Any help would be appreciated. Web Service Single Sign-On
As with many other PPM Web components, PPM Web services is able to integrate with most industry-standard single sign-on (SSO) systems such as CA SiteMinder, Oracle Identity Management, RSA Sign-On Manager, and IBM Tivoli Access Manager through pluggable authentication frameworks. PPM provides a log-in module for SiteMinder. For other SSO systems, additional customization may be required.
You can integrate with SiteMinder using the PPM SiteMinder Log-in Module. When this authentication mode is used, PPM authenticates users to SiteMinder, and does not store user passwords in the PPM database. PPM Server Configuration
From the PPM server side, you can add the following parameters into the server.conf file:
· To allow SiteMinder Login Module to be invoked for Web service user authentication, set the following parameter:
· To choose SiteMinder to be the authentication mode, set the following parameter:
Note: If SiteMinder is chosen as the only authentication mode, any individual user's authentication mode that was set through the workbench user page would be overwritten by this mode.
· To make PPM Web application use single sign-on mode, set the following parameter:
Integration with a Client-Side Log-In Module

To complement the integration with client-side log-in module, follow these steps:
1. Develop a Java Authentication and Authorization Service (JAAS) log-in module that authenticates with the SSO system and receives an SSO token. The token could be set as a private credential in the Subject class.
PPM has already provided such a module: com.kintana.sc.security.auth.SiteMinderLoginModule
2. Create the JAAS configuration file under the $WebServiceToolkit/java/conf directory
SiteMinder {
com.kintana.sc.security.auth.SiteMinderLoginModule required
3. Specify the JAAS login configure system property in the command lines used to invoke the Web services in the compile_client.bat file
java -Dclient.repository.dir=%WSCLIENT_HOME% -classpath
examples.pm.ProjectServiceClient https://localhost:8443/itg/
ppmservices/ProjectService "kevin8"
4. Add logic in the Web service client to invoke JAAS login
public Subject login() {
LoginContext lc = null;
lc = new LoginContext(
" MyCustomModule ",
return lc.getSubject();

5. Add the SSO token as cookie in the Web service client.
Examples: Set a HTTP cookie in axis2 Web service client.
public void setSSOCookie(Stub stub, String ssoToken) {
List headers = new ArrayList();
//Set the required session variable for SSO system
Header header = new Header(
"SMSESSION=" + ssoToken

ServiceClient client = stub._getServiceClient();
Options option = client.getOptions();
6. Call the corresponding method to set the SSO cookie after a stub is created.
7. Make the desired Web service request with the SSO cookie you set

0 Replies
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.