Synchronisation fails from time to time when using OIDC in SaaS with a Self-Managed gateway.
To trigger again the synchronisation the application should be updated or deleted and recreated. This is currently the only way to trigger synchronisation.
However, this has an impact/visibility to customer's end-users, requiring end-users to act on a failure before they even got started using customer's APIs.
It would be useful to see the events and the status of the synchronisation, or a feature that indicates if the synchronisations has been successful and if not, a "retry" button.
---- Dev Notes ----
There are some issues that look similar, which are:
In here there wrote a patch to make it work but it may or may not be the proper fix.
hramihaj and mnoyabon could reproduce this following these steps to check if a fix in the Porta repository was working. Another bug was encountered while doing that test, it is THREESCALE-1791 and it is also explained in that same thread.
To test all these bugs, there is a patch to be able to test the mentioned PR. This patch is not meant to be a real solution, but just to be able to test. It is mentioned here just in case that it is helpful for the team to get a clue of what is wrong and how to fix it.
In Zync there is also a PR with Documentation of an installation guide & Integration guide. This last one can help for anyone who doesn't know anything of Zync. And that one is meant to be merged at some point
- is blocked by
-
THREESCALE-2068 Document Installation guide & Integration guide
- Closed
- is related to
-
THREESCALE-2557 Investigate OIDC issues
- Closed
- relates to
-
THREESCALE-1480 Client ID not registered in RH-SSO
- Closed