Skip to content

Initialize ESPProvisioningProvider with the proper realm (from URL or…#56

Open
ebariaux wants to merge 1 commit into
mainfrom
fix/provision-provider-realm-api-url
Open

Initialize ESPProvisioningProvider with the proper realm (from URL or…#56
ebariaux wants to merge 1 commit into
mainfrom
fix/provision-provider-realm-api-url

Conversation

@ebariaux
Copy link
Copy Markdown
Contributor

… preferences)

@ebariaux ebariaux added the Bug Something isn't working label May 26, 2026
@ebariaux ebariaux linked an issue May 26, 2026 that may be closed by this pull request
Copy link
Copy Markdown
Member

@MartinaeyNL MartinaeyNL left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ebariaux Me and @dominiquekleeven discussed on this "constants" approach, but agreed to not to go for this. 😅

My opinion was that the ESPProvisionProvider itself shouldn't be "aware that realms exist".
Instead, by including the realm in the provisionDevice payload itself, similar to the accessToken,
we only make the provider "realm aware" for this single API request the provider makes.

Alongside that, I think it'd be important for apps to work in multiple realms.
Because now it is locked into a single realm per app.

I'm happy to call if you'd like to discuss.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Use proper realm when building URL for Provisioning Provider

2 participants