Business Objects 4.1 SP7 Java SDK Trusted Authentication

[former_member280521]

Prior to SP7, the format for the TrustedPrincipal secret was along the lines of:

SharedSecret=<long hexadecimal value>

Now in SP7 FP3, the format for the TrustedPrincipal.conf file generated for trusted authentication is:

SharedSecret=

100

<long base 64 value>

The question is when using the method ISessionMgr.createTrustedPrincipal( String user, String cms, String trustToken ) - what is the trust token that is passed to the method supposed to look like?

Prior to SP7, you just passed the hexadecimal value (stripping off the SharedSecret= text from the TrustedPrincipal.conf file. In SP7, failing to login trying any of full contents of file, second two lines (100\n<base 64 value>), or just the base 64 value in the last line.

[denis_konovalov]

I have fixed your tags, please select more careful next time.

[joshua_kuhn]

For anyone else reading this that is seeing the same issue, be sure you are downloading the shared secret while logged into the CMC as 'Administrator'. If you are logged into CMC as a secondary admin user, the 'download shared secret' button will end up downloading a file with improper formatting. Plus the actual shared secret value is wrong. Here's an example from my test system when downloading the same shared secret file as administrator vs a secondary admin user.

[daniel_paulsen]

you should simply be copying the entire string after "sharedsecret=" and pass that.
I am not aware of any changes and you do not have to encode the string in any way.

for example. If your TrustedPrincipal.conf looked like:

SharedSecret=efbfbdefbfbdefbfbdefbfbdefbfbdefbfbd614919efbfbdc393efbfbdefbfbdefbfbd71efbfbdefbfbd52efbfbd027322efbfbd43cba13cefbfbd7416efbfbd2eefbfbd023b4d112d5c261c2fefbfbd627050474eefbfbd30efbfbd4cefbfbd1d0760efbfbdefbfbdefbfbd0a7fefbfbd

Then pass in everything after the "=" sign.

Dan