Skip to content

User consent for Obo.Api.One to access Obo.Api.Two on the user's behalf #1

@johschmidt42

Description

@johschmidt42

Hi!

thanks for the detailed summary how to accomplish the OBO flow on Azure with 3 App registrations. I've done the exact same and it works. However, I was wondering why no consent from the user to is required? Obo.Api.One will access Obo.Api.Two on behalf of the user but no consent was asked? It still works without "Grant Admin Consent" in the API permissions section for Obo.Api.One. The only thing required, is to pre-authorize the client application.

Looking forward to your answer!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions