-
Notifications
You must be signed in to change notification settings - Fork 9
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
let external users approve terms_of_use
themselves?
#291
Comments
@lsloan, can you determine whether the new user is prompted to accept terms of use in the cases where this is |
When I create a user through the regular UI it doesn't set this parameter at all, it's not required. I'm not seeing where the default is true. This is the prompt the user ends up with, at least from the dev instance. This seems like what we'd want, and should be obtained either setting false or not setting. Unless our prod instance is configured differently from dev to not require anyone to accept terms. In that case false or not setting still seems the best we can do. |
From Canvas API docs: `user[terms_of_use]` - Whether the user accepts the terms of use. Required if this is a self-registration and this canvas instance requires users to accept the terms (on by default). If this is true, it will mark the user as having accepted the terms of use.
I don't see |
Problem
When the external user enrollment feature of the API was implemented, one of the keys sent to the Canvas API is
"terms_of_use": true
. Canvas seems to work if that value isn't specified, but at the time it seemed like it would be safer to specify it explicitly.That resulted in the conversation…
Originally posted by @ssciolla in #247
Originally posted by @lsloan in #247 (comment)
Solution
If it makes sense to do so, either remove the
terms_of_use
key from the request or explicitly set it tofalse
, whichever will give the desired behavior.It would be helpful to get @melindakraft's input on this.
The text was updated successfully, but these errors were encountered: