Using the same situation as our friend reported in his question:
invalid_grant: AADSTS50126: Error validating credentials due to invalid username or password
As I understand it, the solutions presented focus on changes and moves within the AAD itself.
But I'm in a scenario where the rules and policies will not change.
As we have an hybrid identity federation scenario … we would recommend to use a single-page application platform with implicit flow or something else from the documentation.
Would there be any documentation available for the third party application, in this case our supplier that currently uses the same flow (ROPC), to adapt its application to this hybrid scenario?
Sorry if this seems repetitive, but I think it would be interesting for the community to have a solution that is viable for the AAD team, as well as for the developers who will have to adapt to these standards and replicate them in their corresponding software.
Tks for your time in advance.
