Jump to content
We've recently updated our Privacy Statement, available here ×
  • Can login as superuser on one node of the cluster but not the other one


    Friendly User
    • Features: JasperReports Server Version: v7.9, v7.9.0, v7.8, v7.8.1, v7.8.0, v7.5, v7.5.1, v7.5.0 Product: JasperReports® Server

    Scenario:

    You've created a cluster of two servers which are connecting to the same repository DB. When going to one node directly you can login as superuser/superuser account but not on the other. What is the reason for this?

    Solution:

    this most likely means you've set up two nodes with two different keystores. When buildomatic or bundled installer runs the installation scripts, it generates a keystore in the user's home folder - .jrsks and .jrsksp. These two files contain the keys to encrypt and decrypt passwords. During each installation a unique key is created if none is found already in the expected location. To amend the situation what you can do, assuming the two users on two nodes are identically named and have same home folder location, is to copy and replace the keystore files from one node to another node. If you have encrypted passwords in config files (context.xml, externalAuth files, quartz scheduler, etc.), then you'll need to re-encrypt them.

    See here for more explanation on this feature:

    https://community.jaspersoft.com/wiki/encryption-jasperreports-server-75#Installing_across_Multiple_Servers


    User Feedback

    Recommended Comments

    There are no comments to display.



    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

×
×
  • Create New...