Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML SBM remembers SmartCard login at login form
SSO + SmartCard with web services set to internal password. Override the Federation server URL to go to IIS on port 443. Set the sbmconnector virtual application in IIS to Accept Client Certificates .
CMS-XML HSSO - Hybrid SSO for SaaS environments- cannot logon as getting Untrusted Endorsing Credentials or Failed to verify signature - certificates expired and need updating
log4j.logger.httpclient.wire=TRACE log4j.logger.httpclient.wire.header=TRACE NOTE: You must remember to set these back to INFO afterwards else you will get performance issues
CMS-XML Dim10: Two client installation node - cannot login through desktop client with error: Credentials lookup failed
If the Dimensions client installation is done on computer that the computer name is MBCS, the desktop client login gives "error: Credentials lookup failed" This issue is cased by the client name being read as MBCS rather than UTF8; some client machine names seem to give more problems than others.
CMS-XML DIM CM: One-time login certificate which includes a tertiary node login (MVS) fails if the @ is in login credentials
DIM CM: One-time login certificate which includes a tertiary node login (MVS) fails if the @ is in login credentials
CMS-XML KM-Dim7: User gets ...invalid login credentials supplied... logging into Oracle Management Server as 'sysman.' Once that is resolved, user may get ... EMSDK-1100 Unable to establish a secure communication channel ... if recently upgraded from Dim 7.1 to 7.1.1
KM-Dim7: User gets ...invalid login credentials supplied... logging into Oracle Management Server as 'sysman.' Once that is resolved, user may get ... EMSDK-1100 Unable to establish a secure communication channel ... if recently upgraded from Dim 7.1 to 7.1.1
CMS-XML Unable to login or promote or deploy after Sept. 11 2012 due to certificate expiry issue
Unable to login or promote or deploy after Sept. 11 2012 due to certificate expiry issue
CMS-XML 403.16 when trying to login after updating the client certificate in SBM
When SBM is setup to use Client Certification Authentication, client certificates will need to be updated periodically. It has been seen where generating the new key does not remove the old key.
CMS-XML IIS 8.x rejects client certificates (or Smart Card) with 403.7 or 403.16 error (Login page gives "Transport error: 403 Error: Forbidden")
Changes in IIS 8.x can cause 403.7 or 403.16 client certificate errors that did not exist in the IIS 7.x setup.
CMS-XML If apply custom certificate to IIS via configurator the next change in configurator results in error: A specified login session does not exist. It may already have been terminated. (Exception from HRESULT: 0x80070529)".
If you have a custom certificate provided by a local authority then once you apply it to IIS via configurator UI it works fine but.... Any subsquent changes to configurator come back with an error within the configurator dialog "Error while applying IIS SSL settings" once they are applied. The logs stated "A specified login session does not exist.
CMS-XML KM-Dim9: Popup message from Dimensions web client logon it asks me to verify a certificate from VERISIGN
KM-Dim9: Popup message from Dimensions web client logon it asks me to verify a certificate from VERISIGN
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs