Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML Password encryption used in the Release Manager components
The Serena Release Manager solution mandates SSO ( Single-Sign On ) configuration , which is controlled by SBM. However, Release Automation/Nolio does not work with SSO yet. That means that Release Control/SBM and Release Vault/Dimensions CM would use SSO via SBM (which uses SHA-256) and Release Automation/Nolio would use its own password storage (which uses 3DES).
HTML Solutions Business Manager 11.4 Security Bulletin
Summary Secure JNDI Datasource Passwords (DEF298499) JNDI datasource passwords are now automatically encrypted using the security algorithm selected for SSO files in SBM Configurator. Encrypt Common Log Database Password on the Application Engine Server (DEF158004)
CMS-XML Readme for SBM 10.1 as of 9th February 2012
The SBM Configurator now enables you to manage encryption settings for SSO configuration file passwords throughout your installation. To encrypt SSO configuration file passwords for components such as the ALFSSOgatekeeper, ALFSSOLogin, and TokenService, use the encryption options on the General tab in the SBM Configurator's Security settings.
CMS-XML SBM 2009 R4 (and prior): How to generate new signed certificate trust keys for SBM and copy them to additional servers as needed (Renew SSO certificates)
... not related to SSO certificate expiration) ... ... . Determine if SSO is currently enabled ... ... select Options | Settings . If Single Sign On ( SSO ) is selected in the Authentication settings area, proceed ... 2. If SSO is not selected ... plan to enable SSO in the future ... ... 2. If SSO is currently enabled ... ... CN=Serena SSO IdP STS, ... Signature algorithm name: SHA ... Replacing Your SSO Certificates ... are using the SSO server that is ... the following Serena Single Sign-on ( SSO ) certificate renewal ... ... that hosts the SSO Engine.
CMS-XML Configuring SSO Protected Hosts
Configuring SSO Protected Hosts
CMS-XML Configuration Utility requires Mashup Manager or SSO setting, even if not installed
Configuration Utility requires Mashup Manager or SSO setting , even if not installed
CMS-XML SSO configuration of SSOLDAPThenInternal fails after upgrade to 11.6.1
SSO configuration of SSOLDAPThenInternal fails after upgrade to 11.6.1
CMS-XML Identifying the SSO token signature hash algorithms
To identify the used SHA methods in an SSO token you can use the following URL (after you are logged in to an SBM system that uses SSO ): http://<insert machine here>/tmtrack/tmtrack.dll?ALFSSOGatekeeperCommand=ShowSSOToken&TokenEnc=pretty Once the page is loaded right click on the empty space in that page and View Source.
CMS-XML Configurator gets null pointer exception after setting SSO LDAP then internal authentication
Configurator gets null pointer exception after setting SSO LDAP then internal authentication
CMS-XML Hybrid Single Sign-On (HSSO) Configuration and Troubleshooting Guide for On-Demand
Hybrid Single Sign-On is available to all On-Demand customers of SBM On-Demand (SSM, Workcenter, etc). The HSSO Client provides a means to authenticate users within the customer’s domain infrastructure, create the session token in house, and then pass the token off to the SBM server running in the cloud. To do this, first a Java keystore is created on the HSSO Client and then the public key is upload in to the customer’s namespace by the SaaS Operations team.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs