Please ask your question on GitHub. ( https://github.com/Rundiz-WP/okv-oauth/issues ).
]]>One more hard coded variable than need UI.
I edited line 127 in file “okv-oauth/App/Libraries/MyOauth/Google.php”:
From:
'&prompt=select_account+consent';
to:
'&prompt=select_account';
Add switch because now it will re promt every time for permission (can be skipped).
]]>Hello,
First: thanks for plugin! ??
Second: Some options are missing. This one can be usefull when OAuth is used in limited by domain enviroment. This will force all OAuth request to be more limited in selected scope (Limit Google, not needed for Facebook). This field can be editable in admin panel as other and have simple validation (have 1 comma and no protocol)
Like how to enable that feature with example: https://stackoverflow.com/questions/10858813/restrict-login-email-with-google-oauth2-0-to-specific-domain-name
Where is some GitHub page ? Nice to have something like that
]]>I DONT want to keep any auth info inside WordPress. Instead I want the auth source to be my CRM.
1) Some business rule triggers and visitor is prompted to authenticate
2) Visitor is prompted for an email
3) Check if it exists in the CRM
4) If not prompt to create acct (submits to CRM)
5) If dont remember password retrieve/regenerate (via CRM)
My expectation is that you have the steps already mapped out and its just a question of where it selects, inserts, or updates the Auth data. Also can we reduce friction by just asking for email, unless accessing preferences where they will have to generate or submit a password? Where will business rules be, how will they be organized and how will it prioritize trigger rules
]]>