In reply to: Daniel Krüger (Cosmo Consult)
Hi Ingo.
you are right these changed with version 2022. I know I've read somewhere about this change but I couldn't couldn't find it again.
The only thing I remember is that applications registered with prior 2022 will work as before but new ones have to be configured using the new options.
I have in mind that the user app context and ist context can be compared to Azure privileges which are granted by the admin (app context) or if they are delegated (user context). The latter one would be similar to an impersonation while the first one would be a "service account".
But I could be wrong. Maybe someone else can confirm this.
Best regards,
Daniel
Hi Daniel,
again thank you for your answer. What you say, makes sense and matches my tests in other systems of ours, where apps having existed prior the upgrade from 2021 to 2022 show a similar behaviour.
So, the user context allows to deliver a more differenciated set of rights. If so, there is the question on how do I differ the user during i.e. the push of new information from an erp to the WEBCON BPS context? Is this still the impersonation tag within the web service used to create the Bearer Token?
I'd assume this but do not think that the scope option will have a function in differentiating the users.
I would love to continue this discussion in order to understand this feature fully. So, your reply or that of others is highly appreciated.
Best, Ingo