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

Adding scope field to generic OAuth #402

Merged
merged 1 commit into from Oct 13, 2020
Merged

Conversation

@dariusk
Copy link
Contributor

@dariusk dariusk commented Oct 13, 2020

Some OAuth providers (like Mastodon) do not use the default "read_user" scope, instead offering a set of custom scopes. The config.ini for generic OAuth now contains a "scope" field, allowing the admin to set the scope manually (it defaults to "read_user" if blank).

I'll have documentation incoming on the documentation repo shortly. Documentation PR is up: writefreely/documentation#31

  • I have signed the CLA
Some OAuth providers (like Mastodon) do not use the default
"read_user" scope, instead offering a custom scope. The config.ini
for generic OAuth now contains a "scope" field, allowing the admin
to set the scope manually (it defaults to "read_user" if blank).
Copy link
Member

@thebaer thebaer left a comment

Thanks @dariusk, this is great! Will merge this now.

@thebaer thebaer merged commit 3493921 into writeas:develop Oct 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
You can’t perform that action at this time.