Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default Microsoft Graph Client Id should be configurable #78

Open
AliveDevil opened this issue Mar 13, 2024 · 4 comments
Open

Default Microsoft Graph Client Id should be configurable #78

AliveDevil opened this issue Mar 13, 2024 · 4 comments

Comments

@AliveDevil
Copy link
Contributor

With different client ids for Cyberduck and Mountain Duck, the SharePoint Site-profile listed here doesn't work in Mountain Duck (x-mountainduck-action is not set as a valid redirect URI for the Cyberduck application).

@dkocher
Copy link
Contributor

dkocher commented Mar 13, 2024

Supposed to be fixed with 755731c.

@AliveDevil
Copy link
Contributor Author

Client Id is still the same:

<string>f40bc18f-cd02-4212-b7f1-15243e4e2ad3</string>

@AliveDevil
Copy link
Contributor Author

Add default-property microsoft.graph.clientid, which can be set to <string>${microsoft.graph.clientid}</string> in this profile?
Would allow removing the duplicate profile in Mountain Duck for OneDrive and SharePoint as well, when using a default-property.

@dkocher
Copy link
Contributor

dkocher commented Mar 16, 2024

Add default-property microsoft.graph.clientid, which can be set to <string>${microsoft.graph.clientid}</string> in this profile? Would allow removing the duplicate profile in Mountain Duck for OneDrive and SharePoint as well, when using a default-property.

I have added x-mountainduck-action://oauth to the app registration of f40bc18f-cd02-4212-b7f1-15243e4e2ad3 as a temporary workaround.

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

No branches or pull requests

2 participants