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 SRA: Configuring SSO documentation correction
SRA: Configuring SSO documentation correction
CMS-XML Configurator gives error "Unable to configure gatekeeper-core-config.xml. This may affect normal functioning of Single Sign-On features." and can't set overrides in Secure SSO section.
Configurator gives error "Unable to configure gatekeeper-core-config.xml. This may affect normal functioning of Single Sign-On features." and can't set overrides in Secure SSO section.
CMS-XML How to enable NTCR or IWA while using SBM SSO
IMPORTANT: The steps to enable NTCR with SSO have changed slightly beginning in SBM 10.1.3. Please refer to the Installation and Configuration Guide in the section called " Configuring SSO and Windows Domain Authentication" for complete details.
CMS-XML 'Generate All' button the Configurator > Advanced Settings > Security > Secure SBM tab is grayed out
On distributed SBM servers that do not have the Serena Single Sign On ( SSO ) component installed, the Generate All
CMS-XML Increasing the RAM allocated to Jboss (change JBoss memory settings)
Monitor the java.exe service in the Windows Task Manager. In most cases, you will see this server running at or below 4GB of RAM. If you noticed slowness in processing orchestrations, SSO authentication, the Application Repository, Common Services etc, it may be that JBoss needs more RAM.
CMS-XML Disabling SSO
If you chose the SSO options during installation but wish to later disable it, follow these steps: 1. Launch Mashup Administrator, and then select Options > Settings . 2. On the Server tab, clear the Single Sign-On (SSO) checkbox.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs