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 Out of network users communicate with JBOSS on port 443
When a firewall is placed between the SBM server and the SBM user, it is not always possible to open JBOSS ports 8085, 8243 and 8343 to allow communication through the firewall. If the SBM JBOSS server (Application Repository, Orchestration Engine, SSO engine, etc.) is installed on a server without IIS or other web server, JBOSS can be setup to use the well-known ports of 80 and 443.
CMS-XML Configuration changes required for Smart Card authentication when IIS is configured to proxy SBM requests
tab in SBM Configurator. This option disables all Tomcat HTTP connectors (8085, 8243, 8343 , 8443). When you enable this option, you must perform the following additional steps to properly configure Smart Card authentication:
CMS-XML CAC/PIV/Smart Card: When users try to login, they get error "This page can't be displayed"
This page can't be displayed Make sure the web address https://myServer: 8343 is correct. Look for the page with your search engine.
CMS-XML SmartCard (CAC) authentication from VM desktop clients to an SBM SSO server breaks after upgrading to SBM 11.4
Username + password authentication using SSO still work, but l ogin attempts via CAC throws the following error on the VM client side: SSO/CAC Login Error: Connection exception using SSLCLIENTAUTHURL "https://or-rgering-w2k8: 8343 /idp/services/Trust": The specified request failed
CMS-XML Cannot deploy large Process App on Windows 2008 R2 - IIS 7.5. Error: " a Transport error 404 - Not found "
Server log snippet ( By default this log can be found here on the Application Repository server C:\Program Files\Serena\SBM\Common\jboss405\server\default\log\server.log ) 00000: INFO 2011-07-11 09:37:28,269 org.apache.coyote.http11.Http11BaseProtocol -- Starting Coyote HTTP/1.1 on http-0.0.0.0- 8343
CMS-XML Serena SSO/CAC Setup through port 443 Only
When a firewall is placed between the SBM server and the SBM user, it is not always possible to open JBOSS ports 8085, 8243 and 8343 to allow communication through the firewall. The JBOSS components (SSO, Application Repository, Orchestration Engine, etc.) can be installed on a separate server without IIS such that JBOSS Tomcat web server is configured to use port 443. This configuration is straight forward and easily managed.
CMS-XML VIDEO: How to setup CAC / Smart Card client certificate authentication
JBoss Ports: In SBM Configurator, on the JBoss Server view, verify that you have an HTTPS port (by default 8243) and a HTTPS Client Cert Authentication Port (by default 8343 ). Single Sign-on: In SBM Configurator, on the Authentication view, and make sure that Single Sign-On is enabled. These videos were created prior to SBM 11.0 when JBoss was used so there are references to the following folder paths throughout.
CMS-XML How to configure the Cipher Strength for SBM JBOSS
Locate the SSL connectors. There are one or two SSL connector port definitions: one for default port 8243 and default SSL port 8343 if smart card/client authentication is enabled.
CMS-XML Enabling Automatic Smart Card / Common Access Card (CAC) Log In
By default, the client-cert (two-way SSL) port is set to 8343 . Perform the following steps to change the Federation Server URL port to use the client cert port value. Note:
CMS-XML How to set up SBM behind a proxy
User Workspace: Port 80 and/or port 443 With Serena Single Sign On (SSO) enabled, port 8085 and/or 8243 is necessary because the user will get redirected to the SSO login page. With Common Access Cards (CAC) or PIV cards, the user will also need access to port 8343 .
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs