Hasan Tariq

Hi,

It is coming from the Query Builder but only becomes an issue when both Builder and Source Addon are active at the same time.

I noticed if I disabled the Source Addon but let the Builder remain active it still solves the issue and the datepicker goes back to normal.

Thanks

Ok on more testing it strangely happens when you have both this (GF source addon) and your Query Builder Addon running at the same time.

Deactivate either one and it goes back to normal.

• This reply was modified 5 years, 11 months ago by Hasan Tariq.

The response of both the above plugin developers to this issue is extremely disappointing choosing to ignore and/or shift blame to one another as opposed to actually even showing the slightest willingness to find a solution. Shows how much they care for users and developers considering these for production sites should be mindful of this.

For the users struggling with getting their sites working after updating to UM2.0, here is a solution I can offer to get things going temporarily hopefully until this gets resolved:

– In UM settings, ensure you uncheck ‘Pages’ under access. With this you will forgo the ability to restrict access to pages individually. However this will solve the redirection loop.
– With UM2.0 you can restrict access to categories and those access restrictions will flow on to any posts or pages you assign to them. WP doesn’t have categories for pages so you will need to solve this first.
– Now install a good plugin which lets you assign categories/tags to pages.
– Create a category for each access level you want to have.
– Add the relevant pages you want to restrict to the right categories. In other places you can use the shortcodes (which will also need to be updated with the prefix “um_” since the developer didnot care to include that in the auto-update if you are updating to UM2).

Hope this works for you as it works for me.

Hi @auth0josh,

Many thanks for your reply. All makes sense now.

Last question, given that I need to use the same database for all applications to share users:

What is the recommended workflow when setting up the plugin on a new site?

Should I run the wizard as a new install with user migration on each site and then switch the database from the Auth0 dashboard?

OR

Should I use the import settings option in the wizard on first install. Is that option for importing options in to another instance of the same site or to add an additional site to the same network of sites with the same database connection. Which is my use case.

Thanks

• This reply was modified 6 years, 2 months ago by Hasan Tariq.
• This reply was modified 6 years, 2 months ago by Hasan Tariq.
• This reply was modified 6 years, 2 months ago by Hasan Tariq.

Hi @auth0josh,

I have auth0 working across 4 sites. But there is one thing I am struggling with if you can shed some light on this.

Let’s say I have 4 sites. Each site has its own users (in thousands). 50% of those users also have accounts on other sites in the group. They have all signed up independently for each site. The email address would be the same but password could be different.

Now I want to use auth0 across the 4 sites and offer SSO to all users across the sites.

What I am struggling with is the database connections from the auth0 dashboard.

Should each application (of 4), have access to all the databases of the others? So each app has access to 4 databases. I have tried this but this doesn’t work and only the top-most database in the list gets queried and the login doesn’t work if the source of users is from one of the other databases. It throws an invalid password error and I can see in the log it is using the wrong database.

Or:

Should each application (of 4), have access to only 1 database, the same database? So I disable the other 3 databases and only use 1. The problem with this approach is, existing users created via one of the other databases can’t log in.

Thanks, will appreciate your help on this.

Hi Josh,

Thanks for your reply.

So can you confirm the first time I setup the plugin on an existing site, lets say with thousands of users, all of those will get migrated in to Auth0?

Is it possible to manually run the migration periodically to update the database?

Thanks,

Hasan

• This reply was modified 6 years, 3 months ago by Hasan Tariq.

Hi Josh,

We are using SSO to login between multiple WordPress sites only at this stage.

I do have the setting you mention turned on.

Thanks,

Hasan

Hi Josh,

Everything works now except the SSO between two sites seems to fail.

The log says ‘Failed cross origin authentication’ – ‘Login required’.

The same login works on both sites through Auth0. But if you are logged in to one, it does not log you into the other one.

SSO is enabled across both in the settings. Can you please help with this?

Thanks

Note: I had this working back in December 2017. So not sure if I am missing something this time or is it something in the plugin.

Hi Josh,

Thanks for the update. I have tried this can login now but have some other issues:

– Confirmed database connection works correctly using ‘Get User’ and ‘Login’
– However, login creates a new user in the format of the following instead of matching against the exact same username/email already in WordPress

[email protected]

Also, it seems the connection only works when algorithms on both ends are set to HS256.

Hi @auth0josh,

I am starting again with a fresh install: both plugin and tenant.

API EXPLORER BIT
Tried this. Initially API Explorer doesn’t show as an option by default as shown in the screenshot. However, I went to ‘APIs’ in the dashboard and authorised a test client. Then it started showing up. Did everything still no luck. The log still says algorithm not allowed.

IN RESPONSE TO YOUR QUESTIONS
– Just started again with a fresh install. Made no changes except the one described above.
– Auth0 account was created mid-December. However, I deleted the tenant and started with a new one just now.
– Yes, I am migrating the database. I tested this and it worked before the API update. The only change that I make for this to work is disabling ‘Migration IPs whitelist’ in the WP Plugin Settings (Advanced). The whitelist doesn’t let me add all the IPs stated in ‘Connections > Database > Custom Database’. It just lists 2 IPs in WP which doesn’t allow it to get through.
– I am logging in via the shortcode [auth0].

@auth0josh,

Also, I’d like to mention one other thing I noticed.

As you updated the plugin after I had already installed it on a site. Prior the update, when I tested the custom database connection from the web console using ‘Get User’ and ‘Login’ it worked. However this was when it couldn’t connect to server to actually log in via the widget.

When I updated the plugin on that site, after login it created a new user (instead of matching against the one already in the system) in the following format:

– [email protected]

If I try to use a social login like Google with the current setup, it does the same as opposed to matching the same email against the same already inside the WP database.

Hi @auth0josh,

Thanks for your reply.

I did come across that post and have tried it already (twice). The issue still persists:

– Setting algorithm on both ends to RS256 (which the plugin sets by default on install)
– Setting algorithm on both ends to HS256

If I try logging in via the widget it says incorrect password.

When I test the custom database connection from the Auth0 web console using ‘Login’ or ‘Get User’ I get the same result. The log in the WordPress plugin says:

– migration_ws_login 0 Algorithm not allowed
– migration_ws_get_user 0 Algorithm not allowed

If I look at the log inside the Auth0 web console, it thinks:

– Failed Login (invalid email/username) Wrong email or password.
– Failed cross origin authentication Wrong email or password.

BACKGROUND
I had a fully working instance using the old APIs in December ’17 on a couple of test sites. When I was getting ready to roll the same out on production sites it seems to have stopped working.

Hi there,

I am getting the same issue. The output gives me either an ACF: false or an empty ACF: [].

Could you assist please?

Thanks,

Hasan