After CAPC and CABI upgrade users synchronization and automatic login not working

Document ID : KB000110019
Last Modified Date : 08/08/2018
Show Technical Document Details
Issue:

After the upgrade to CA Performance Center 3.6.0, and the update/reinstall of the CA Business Intelligence JasperReports Server content package (capm_reports-xxxx.zip file), existing users cannot access reports and dashboards directly from CA Performance Center as before the upgrade. They are required to log in to CABI to get the report.

The following error message is printed in CABI logs:

2018-08-07 10:55:31,594 ERROR TokenService,http-nio-8080-exec-7:162 - Token is already used 
2018-08-07 10:55:31,596 ERROR ExternalAuthenticationProxyFilter,http-nio-8080-exec-7:90 - Exception processing token 
2018-08-07 10:55:31,597 ERROR CABIUtil,http-nio-8080-exec-7:69 - com.ca.bicoe.cajasperserver.common.util.CABIExceptionForRunTime: org.springframework.security.authentication.BadCredentialsException: Token is already used 

at com.ca.bicoe.cajasperserver.preauth.sso.ext.filter.TokenService.validateTokenTimeStamp(TokenService.java:164) 
at com.ca.bicoe.cajasperserver.preauth.sso.ext.filter.TokenService.processToken(TokenService.java:92) 
at com.ca.bicoe.cajasperserver.preauth.sso.ext.filter.ExternalAuthenticationProxyFilter.doFilterreq(ExternalAuthenticationProxyFilter.java:132) 
at com.ca.bicoe.cajasperserver.preauth.sso.ext.filter.ExternalAuthenticationProxyFilter.doFilter(ExternalAuthenticationProxyFilter.java:80) 
at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:343) 
at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:260) 
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) 
at com.jaspersoft.jasperserver.war.UserPreferencesFilter.doFilter(UserPreferencesFilter.java:235)

 

Environment:
CA Performance Center 3.6.x
CA Business Intelligence JasperReports Server 6.4.2
Cause:

capm.properties and capm.jks files was not regenerated during CABI content package installation.

The CABI content install script checks if capm.properties and capm.jks files already exist. 
If yes, then a message is showing "CA Business Intelligence SSO keystore and properties files already exist. 
Regenerate files (Yes/No)? [No]:" (default answer is No)

Resolution:

During CABI content package installation, select the option to regenerate the capm.properties and capm.jks files.

Follow the steps from CA Performance Management documentation chapter "Install Reports on the CA Business Intelligence JasperReports Server":

Copy the capm_reports-xxxx.zip file to the CABI JasperReports Server host and unpack it into a folder for the reports.
Run the Install.bat (Windows) or Install.sh (Unix) installation script.


The CABI content install script checks if capm.properties and capm.jks files already exist. 
If they exists, this message will prompt: 

"CA Business Intelligence SSO keystore and properties files already exist. Regenerate files (Yes/No)? [No]:"   (default is No)
Select "Yes" 

When completed, copy the newly generated files from CABI server folder <CA Business Intelligence>/apache-tomcat/webapps/jasperserver-pro/WEB-INF/config to the following location on CA Performance Center server: <CA Performance Center>/PC/webapps/pc/WEB-INF/CABIKeystore 

Additional Information:
The following lines should be present in the capm.properties file on both CAPC and CABI: 
token.save=no 
token.expirytime=86400 

These lines are required to avoid the message "Token is already used" and allow correct user synchronization between CAPC and CABI.