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 REST widget doesn't work when using NTLM w/ or w/o SSO and with Firefox
REST widget doesn't work when using NTLM w/ or w/o SSO and with Firefox
CMS-XML RQM REST services do not work with SSO
The RQM REST services do not authenticate successfully through SSO. The work around is to use a service account which is known to both SBM and Dimensions RM so the user will be authenticated by Dimensions RM and not through SSO .
CMS-XML RM appears to utilize SSO token for REST and Web Service calls
RM validates SSO tokens when " SSO " login source is enabled. If the customer doesn't use SSO in RM - disable the login source.
CMS-XML Rest Grid fails to send request to server
Under some circumstances the SSO tokens may expire before the login session does, and REST Grids fail with an error message along the lines of "Unknown error received from <long URL> (401)
CMS-XML ALM RQM 3.5 bug in getRMCollections Rest Widget.
Issue #1) It looks like the "Use SSO authentication" is not being used correctly, the logs shows useSSO:false regardless whether that box is checked or not (one example of log is the SerenaRQMServices.log). Issue #2) It looks like whether the "Use SSO authentication" box is checked or not, we can connect with either/both SSO or/and non-SSO user.
CMS-XML Making a call through the SBM Proxy using JavaScript how can I control whether the SSO Token is added to the request header or not?
When you do this you have to use the sbmproxy to avoid cross site scripting issues but depending on your needs you might not want the SSO token to be included in the header of the request you're going to. A good example where you might not want the SSO token included might be when making a rest call to another Serena product that uses SSO . You might want to supply your own username/password in the query string or just the existance of the SSO token in the header causes unforseen problems.
CMS-XML Changing sso keystore password in configurator doesn't change custom authenticators in configuration.xml
For instance I added this to my configuration.xml file to do cac. After changing the password in configurator my setting below still said changeit where all the rest that used the same keystore said the new password.
CMS-XML REST Grid and PDF Widgets: jakarta Settings when NTLM Authentication is Used
REST Grid and PDF Widgets: jakarta Settings when NTLM Authentication is Used Change settings in the Select the If Single Sign-On ( SSO ) is enabled, clear the
MS-WORD REST Grid and PDF Widgets: jakarta Virtual Directory Settings when NTLM Authentication is Used
Change settings in the Authentication Methods dialog box if necessary: Select the Integrated Windows authentication check box. If Single Sign-On ( SSO ) is enabled, clear the Anonymous access check box.
CMS-XML Security token is sent even though Use SSO Authentication check box is not selected in Composer
If it is not selected, the security token is not added to HTTP header (this keeps the token from being sent when SSO is SBM-enabled, and is done so for security reasons). This prevents SBM from inadvertently passing the SSO token to non-SBM REST services. (Some services will actually fail if the SBM SSO token is present in the header when not expected).
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs