Launch into Release Control from Service Manager without logging in to RC (1268 Views)
Reply
Occasional Advisor
Emily McMullin
Posts: 7
Registered: ‎10-15-2009
Message 1 of 3 (1,268 Views)
Accepted Solution

Launch into Release Control from Service Manager without logging in to RC

Greetings,

Let me first start by saying that LW-SSO is a new concept to me as a SM implementer. 

 

Our customer is looking to allow the following functionality :

 

While in HPSM, click the link for the RC calendar and have it launch without requiring a user entered login to RC.

 

1. Can you please explain the function of LW-SSO between HPSM and RC?

2. Can this use case be accomplished for a) the RC Calendar b) launching into impact analysis, scheduling, etc in RC without re-authenticating?

3. Can you configure RC Single Sign On (Trusted Sign on ) directly into RC ?

 

For the purpose of this discussion, assume that the user has identical credentials in both systems. 

We are currently seeing the RC login screen after following the steps outlined in docs:

HP Release Control User Guide pp 512, 540

HP Service Manager Help > Integrations > Configure LW-SSO in Service Manager

HP Service Manager Help > Integrations >Configure LW-SSO in Release Control

 

I appreciate any help you can provide.

Emily

Please use plain text.
Occasional Advisor
Emily McMullin
Posts: 7
Registered: ‎10-15-2009
Message 2 of 3 (1,268 Views)

Re: Launch into Release Control from Service Manager without logging in to RC

Well, we validated this in the Surgient system. Now the question is - does this work if RC and HPSM are on 2 separate instances of Tomcat?

 

Please use plain text.
Valued Contributor
J_Stagaman
Posts: 71
Registered: ‎04-30-2010
Message 3 of 3 (1,268 Views)

Re: Launch into Release Control from Service Manager without logging in to RC

@Emily:

Yes, it does when SM and RC are on separate instances (RC using it's embedded Tomcat and SM webtier configured on a separate server). The Surgient lab is actually configured so that SM deployed on the RC embedded Tomcat, but that isn't actually a supported configuration per the compatibility matrix.

 

NOTE: The RC components are not served from the SM Web Tier., each user must be able to directly connect to the Release Control server in order for the embedded Change Calendar and Change Assessment functionalty to work, or to launch Change Calendar. When a ticket is displayed, the RC server is directly accessed by the browser to display RC components. If you are in a firewalled environment, clients must be able to access RC.

 

 

Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation