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 After upgrade to SBM 10.1.4.x, login screen gives "Transport Error: 403 Error: Forbidden"
Transport Error: 403 Error: Forbidden If you check the SSO- IDP .LOG located in [SBM INSTALL DIR]\common\jboss405\server\default\logs, you will see the error below. Error acquiring security token: Transport error: 403 Error: Forbidden
CMS-XML 403.16 when trying to login after updating the client certificate in SBM
403 .16 when trying to login after updating the client certificate in SBM
CMS-XML Login page gives "Transport error: 403 Error: Forbidden"
Login page gives "Transport error: 403 Error: Forbidden"
CMS-XML Some users get "Bad Request" error when attempting to login when they get redirected to the IDP login url.
Some users get "Bad Request" error when attempting to login when they get redirected to the IDP login url.
CMS-XML SRA: Jenkins Plugin: SSO: Circular redirect to 'http://myssoserver:8085/idp/login' error occurs
SRA: Jenkins Plugin: SSO: Circular redirect to 'http://myssoserver:8085/ idp / login ' error occurs
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")
IIS 8.x rejects client certificates (or Smart Card) with 403 .7 or 403 .16 error ( Login page gives "Transport error: 403 Error: Forbidden")
CMS-XML VM Configure Project Login source needs to be able to use and create SSO URIs containing "idp"
As of SBM 10.1.3, the preferred way to communicate with an SSO server running on SBM is via the webapp "idp". Unfortunately Version Manager's Login source screen in Configure Project does not allow for this, as it does not expose the URI itself but constructs one behind the scenes based on information provided to the UI. This means VM continues to use the webapps "TokenService" and "ALFSSOLogin".
CMS-XML VM I-Net Web Client login fails with HTTP ERROR 403 for servlets using an SBM SSO server for authentication
The security enhancement restricts access to the SSO Login web page to a list of authorized servers, which by default consists of just the SBM server itself. To use PVCS VM with this SSO server, the DNS name of the VM server has to be added to the SSO Protected Hosts
CMS-XML Version Manager SSO Login Error: Connection exception using TOKENSERVERURL "...": Received fatal alert: bad_certificate.
14:17:28 May.09.16 [Error] SSO Login Error: Connection exception using TOKENSERVERURL "https://sbm-10121:8243/ idp /services/Trust": Transport error: 403 Error: Forbidde n
CMS-XML DA configured with SSO gives error 403 - Forbidden at logon
After installation, upgrade or rehost, DA users can no longer login . This applies to configurations using SBM for SSO. Attempting to navigate to the login page gives an HTTP 403 Error - forbidden
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs