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

Release 3.6.0 #475

Merged
merged 100 commits into from
Jun 5, 2018
Merged

Release 3.6.0 #475

merged 100 commits into from
Jun 5, 2018

Conversation

joshcanhelp
Copy link
Contributor

NOTES

  • Passwordless was reconfigured completely to use the combined Lock library (currently hard-coded to 11.5). All current settings will be migrated to the new configuration so your login process should not change. Lock initiation has also been refactored to improve maintainability and adhere to WordPress standards.
  • The Setup Wizard has been adjusted to more clearly explain the process and options available. This only affects new installations using the Setup Wizard for configuration.
  • The settings page has been rearranged and improved overall. New settings descriptions have also been added along with links to documentation, where appropriate.
  • State validation was added to both login flows; nonce validation was added to sites using Implicit flow.
  • OIDC compliant Applications should now function as expected (though this setting is not yet activated by default on installation). OpenID Connect login is now possible by turning off the Client Credentials grant for your WordPress Application.
  • Dashboard widgets have been removed. This can easily be added back as a plugin, if needed. Please contact support if you need assistance with this.
  • A number of new hooks have been added, please see our docs page on extension for a complete inventory with examples. This includes the ability to support refresh tokens.
  • Federated logout has been removed.

Closed issues

  • Expose a configurable toggle that allows Users to state if federated logout should be used #471
  • Updating to 3.5.2 - Fatal error: Uncaught Error: Cannot use object of type stdClass as array in /app/wp-content/plugins/auth0/lib/WP_Auth0_DBManager.php on line 225 #464
  • Autoloader performance issue #461
  • Bad request does not raise error #432
  • Widget URL changes don't save when you are using passwordless #430
  • Deprecate oauth/ro endpoint #410
  • Handling errors #403
  • Fallback /api/v2/users/{id} to /userinfo #401
  • CORS errors #400
  • Provide Resend verification email only for DB connections #345
  • SSO disabled, Single Logout enabled causes users to get logged out automatically a few seconds after logging in #336
  • French translation : html characters #309
  • "Invalid authorization code": Access token is requested twice in a row, breaking the login flow #305
  • Make state work after SSO login #302
  • Is there a way to use Refresh Tokens and Wordpress? #296
  • Only decode the payload before user profile fetch in login manager #283
  • redirect callback errors #280
  • Linked Users won't be able to login using implicit flow and pipeline 2 #272
  • Normalize use of shortcode and widget #260
  • Wrong z-index on modal error message in manual setup #252
  • Logout does not work when Wordpress is locked down (private site) #39

Added

Changed

Deprecated

Removed

Fixed

…rect; added WP_Auth0_LoginManager->die_on_login() to handle login errors better
123456789012345678901234567890123456789012345678901234567890123456789012
Added a get_state method to WP_Auth0_LoginManager to get and parse the
state parameter as an object. Added 'state' to allowed query_vars.
WP_Auth0_LoginManager was not processing errors well, was poorly
documented, and might have been improperly exposing error messages.
Incoming URL param errors from Auth0 and configuration issues are caught
earlier in the login process. Error message are not exposed to the
user; instead they are logged for an admin. Thrown errors are
standarized and listed in docblocks.

Fixes #305
The implicit login flow redirects to the login page to handle the
response from Auth0. This caused the cookie to be set to a new value
before the state being returned is checked. The state was also not
urldecoded so "=" chars were being received as "%3D" and were not being
base64 decoded properly.
Documentation for the plugin resides in mulitple places - auth0.com
docs, wp.org readme, GitHub readme - and this commit is part of an on-
going effort to consolidate and clarify. This commit removes the
installation instructions on wp.org, pointing to the docs site instead.
It also updates the screenshots and adds information about support to
the FAQs. This commit also clearly points the GitHub readme to docs
in a few cases and updates the dev instructions.
Admins settings have confusing wording, inconsistent behavior, and
broken links and translation. This first PR refactors the description
system to be more straight-forward, adds HTML generation functions for
consistent field outputs (used in future commits), adds settings page
description translation, and fixes a few other minor code issues.

First of a few smaller PRs to replace #396
State generation, specifically cookie storage, needs to happen before
any output. The previous arch was ok for login page generation but
failed with a "headers already set" error if used in the shortcode.
This addresses the issue by storing state earlier and getting the
value later.
Originally was generating and setting a nonce value in a state object,
then checking that nonce on return from Auth0 instead of checking the
entire state parameter.
Adding get_lock_connections and add_lock_connection for working with
separated options field. reordering option defaults, remove comments,
add docblocks
This field was for an audience value used with the Management API. This
value should never change and should not be user-configurable.
The dashboard widgets clutter the admin, do not display usable data,
and create an unecessary maintenance burden. This functionality can
easily be re-added via a plugin if necessary.

This commit will remove the dashboard widgets output, remove related
settings, and add TODOs for proper deprecation.
This commit will remove duplicate error messages when the plugin is not
setup, use proper HTML format for error messages, and sanitize URL
parameters that are output in messages.
Non-breaking change to centralize asset URLs and remove duplication
Setting names were incorrect, confusing in some cases, and used
inconsistent capitalization.

Rewrite setting names and adding proper translations. Add opt names to
the settings array for more simple HTML output (upcoming PR). Add a
filter to add or modify settings array.
Move the JS that POSTs auth data back to the WP site to it's own file. Better enqueuing for login JS and CSS.
Removes the passwordless method and CDN URL settings. Method is removed to simplify the wp-admin and move passwordless management to the Dashbaord. Passwordless URL is hard-coded to new combined Lock, removing the settings field to change that as well. Going forward, Lock will use the same library for both login form types. Also added a DB version bump and migration script to modify the connections setting so the login form will work as expected after a plugin update. Added a handful of TODOs that will be better suited for a future branch (same release).
joshcanhelp and others added 26 commits May 3, 2018 15:04
- Revise language throughout setup wizard
- Stop forcing auto install
- Do not show configuration nag on wizard page
- Add `required` for various required form inputs
- Add `password` input type where appropriate
- Fix broken auto install button
Correcting input field height on settings pages for IE
Release 3.6.0 - CHANGELOG, version number, and WP.org readme
@joshcanhelp joshcanhelp added this to the 3.6.0 milestone Jun 5, 2018
Copy link
Contributor

@lbalmaceda lbalmaceda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎊

@joshcanhelp joshcanhelp merged commit 84f8307 into master Jun 5, 2018
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants