PentahoTA configuration

The external applications and the corresponding users that are allowed to use the mechanism can be configured in a file called pentaho-transparent-authentication-mappings.json that must be placed in $PENTAHO-ROOT/pentaho-solutions/system. The file must comply to the following format:

    {
        "testApp": {
            "usernamesMap": {
                "testUser": "pentahoUser"
            },
            "applicationName": "testApp"
        },
        "app1": {
            "usernamesMap": {
                "user0.1": "pentaho4",
                "user0.0": "pentaho3"
            },
            "applicationName": "app1"
        },
        "showcase": {
            "usernamesMap": {
                "user0.2": "admin",
                "user0.1": "pat",
                "user0.0": "suzy",
                "user0.3": "tiffany"
            },
            "applicationName": "showcase"
        }
    }  

For security reasons, any request for a login ticket must respect some form of mutual authentication between the two peers involved (the “external app” and Pentaho). Currently, for this purpose, it is assumed that request parameter authentication is enabled in Pentaho. Every request for a ticket must carry the authentication parameters, so the complete format should be something like the following:

http://<pentaho-base>/pentaho/Login?userid=admin&password=password&generate-ticket=1&app=showcase&username=user0.2

<< Usage    |    Up to PentahoTA home     |     Change log >>