Unable to access /KMS or /kms
Originally Published: 2008-01-17
Last Modified: 2023-09-25
Article Number
000052726
Applies To
RSA Key Manager Server
WebLogic 9.2
Issue
Unable to access /KMS or /kms
/KMS returns a "404 - Page not found" error, and hitting /kms redirects to /KMS, which then fails.
Unable to access /KMS or /kms
/kms is redirecting to /KMS, which is unavailable.
Cause
kms.war was deployed instead of KMS.war
Tomcat is not redirecting correctly. 

On the application server, edit <Tomcat install folder>\conf\workers2.properties to add the following Key Manager Server and Tomcat Uniform Resource Identifier (URI) entities

Within the workers2.properties file, there is entries similar to:

#Map the Key Manager Server to the Web server uri space
[uri:/KMS/*]
#Map Tomcat documentation to the Web server uri space
[uri:/tomcat-docs/*]
#Map the Access Manager Administration GUI to the Web server uri space
[uri:/admincfg/*]

With the above example make sure to use https:<servername.com>/KMS/    - note the ending slash.



Resolution
Deploying a war file is case sensitive, so if you deploy a file called kms.war, you will access the application by reaching /kms, and if you deploy a file called KMS.war, you will access the application by reaching /KMS.

Because RSA Key Manager web application uses internal redirection, the war file deployed MUST be names KMS.war, not kms.war.
Make sure to hit https://server/KMS/ rather than https://server/KMS

Related Articles

Trending Articles

Don't see what you're looking for?