@quentin-castel
active 3 years ago-
quentin.castel replied to the topic JWT is not valid error from 'Client credential' API in the forum Access Management 3 years, 3 months ago
Hello Tony,
We try to centralise our support efforts to TPP into a single place. We choose to provide support only via slack, in the Open Banking workspace.
You can register here http://signup.openbanking.space/
The channel that we use for support is #forgerock_supportSee you there!
Quentin
-
quentin.castel replied to the topic OpenBanking Reference App Support in the forum General Discussion 3 years, 11 months ago
In case someone else found this post:
we contacted Jude directly via the OB slack workspace http://signup.openbanking.space/. You will find all the information you need here: https://backstage.forgerock.com/knowledge/openbanking/home
See you soon!
-
quentin.castel commented on the post, How to set up an OAuth2 provider with ssoadm 6 years, 2 months ago
Please note that the REST example above is for OpenAM 12.
Since OpenAM 13, as the resourceTypeUI is now required in the policy json representation, you will need an extra step to create an OAuth2 policy (see
-
quentin.castel replied to the topic Public/Private Areas in Web Sites in the forum Access Management 7 years ago
Hi kgolding,
If I well understood your use-case, the “Not enforced URL” on the agent profile should do the job.
This feature will configure the agent profile in order to avoid calling the OpenAM authentication and authorization modules: It will detect that this kind of URL shouldn’t be protected and won’t redirect your users to OpenAM.
You can…[Read more]
