-
Notifications
You must be signed in to change notification settings - Fork 22
Support for other Azure Clouds #191
Comments
I could also utilize this as well |
Thanks for your report. We plan to support other Azure Clouds, but it is not on our roadmap yet. We will complete the documentation to indicate that only Azure Public Cloud is supported at the moment. |
I believe you can support this by making an api request to https://odc.officeapps.live.com/odc/v2.1/federationProvider and specifying the domain as a parameter. You can see how I've done it in himmelblau in the |
@MrDaGree or @jibel could you confirm this is correct using this simple python script? #!/usr/bin/python3
import requests
import json
url = 'https://odc.officeapps.live.com/odc/v2.1/federationProvider?domain=%s' % 'XXXXX.onmicrosoft.com'
resp = requests.get(url)
parsed = json.loads(resp.text)
print(json.dumps(parsed, indent=4)) Replace |
I can confirm that the output of that query matches the cloud that we are in. But making a http request for that seems like overkill to me, we just need to be able to configure the endpoint in |
We too will need this, as AAD-integration is the main reason we are looking at Ubuntu in the first place. |
Check out Himmelblau: https://youtu.be/rSeHxs0JX58 |
And catch my SambaXP talk (for free) about it tomorrow: https://sambaxp.org/sxp-2024-faq |
Could someone give me a crash course on how to build this project? CONTRIBUTING.md is not helpful, but if I could build it I might be able to piece together an acceptable PR for this. ..Or at very least I could hard-code it to our GovCloud URL and see if that solves my requirement :) |
I've opened PR 500 that adds this functionality, though the system is saying I haven't signed the CLA (I have, many times now). If anyone is interested in testing I can send deb packages or instructions to build. |
I work for a company that is required to use Azure GCC High and it appears that the endpoint is currently hardcoded to the Azure Public Cloud. This means we are unable to evaluate aad-auth for our users.
It would be nice if the endpoint were configurable alongside the existing configuration.
The text was updated successfully, but these errors were encountered: