Realm in Ajax calls

[roelstorms]

Hello,

I have had issues with the fetching of the access token and the userinfo object in the cb-basic.html. I was prompted with a basic authentication form due to a 401 reply from OpenAM. Apperently I had to add the realm as a GET parameter. Next I had issues in fetching the userinfo object. Adding the realm to this ajax call resolved the issue as well.

I have tried this code before when testing with OpenAM12 and then it worked like a charm. However, on OpenAM12.0.2 I need the realm to be added for everything to work.

So the codechanges were quite simple:
url: server + openam + access + "?" + encodeQueryData({ "realm": client_realm })

and

url: server + openam + info + "?" + encodeQueryData({ "realm": client_realm }),

It would take a lot more effort to do a pull request and push my changes. So for this simple issue I think that is overkill.

Kind regards,

Roel

[roelstorms]

Ps: Thanks for the awesome test application. Makes my life a lot easier!

[dgoldssfo]

Roel, I filed OPENAM-8780 on the ForgeRock Jira to track this. Thanks for reporting it and for providing the workaround.

Regards,

David Goldsmith
Senior Technical Writer
ForgeRock

[roelstorms]

Hi David,

Is this an OpenAM bug or are they correct in assuming that the realm is provided in the ajax calls?

Kind regards,

Roel

[dgoldssfo]

Hi, Roel,

I assume it is a bug in the OpenID sample (which is part of the OpenAM doc) and not the OpenAM code line. The bug I filed is a doc bug - if you have a look at it, it's pretty much just a copy and paste from your first post here.

Thanks,

David