rgorrie

I can confirm this is an issue.

On clone (using NS Cloner), WPMembers tries to insert options before the site/tables exist. making the changes Jonathan recommended worked like a charm.

Thanks Jonathan!

This problem was related to using a current version of bootstrap (3.4)

MEC appears to use an older version

I created a function that disabled bootstrap on MEC pages and it went away

Awesome! Thanks so much

Just looked further on blog posts:

To access Canadian institutions, existing customers must include ‘CA’ within the countryCodes array during Link initialization. Check out the docs for details on how to access currency codes and an improved, EFT-friendly Auth schema.
https://blog.plaid.com/plaid-in-canada/

Is there an array in a file I can add this to? If you can point me the right way, I would appreciate it

Hey @auth0josh

Wanted to bump this thread. What IS the best way to ensure multiple systems stay sync’d to Auth0 in real time?

We have 3 different platforms: WP, an SPA, etc that use Auth0 as the “keeper of truth” for all app/user data and each system can update user info and meta as they require. This is currently done via the Management API

Problem is, if one system updates a user, the other 2 systems become out of sync for a while b/c they are still running the same session post-login

So what’s the best approach?

1. Is there an easy way in WP or other systems to “flush” the token/object for a user so it refreshes and syncs the metadata?
2. We’ve seen the get_auth0userinfo( $user_id ); Is there a set_auth0userinfo() or do we have to use the examples you gave earlier to write everything custom? Specifically looking at app/user metadata.
3. Should/can auth0 push new tokens/app_meta via hooks on change?
4. Other

Just trying to wrap our heads around the best approach as we started using Auth0 on one platform and the other 2 got layered in later. It’d be nice if there was a simple way to “refresh” a user as needed from a single point of control

So this actually brings up a question for me!

We have extended login (14 days) AND we want control to be able to disable accounts immediately. From what we’ve experienced the wp Auth0 object only refreshes every 24 hours and wp thinks the user is ok based on its internal checks as no “login” happens.

So we developed routines to do refreshes at the start of each session. Does auth0 already do this (refresh token every session start) and we wasted our time? It doesn’t seem like it but happy to be proven wrong

Also, to be clear, beyond SSO we needed to transfer data from machine to machine so part of the above is related to management api

Thanks

We did this via the Auth0 management api

We created some basic wp functions that do simple things

1. Get token
2. Get Auth0 user and meta
3. Set Auth0 meta

Then you use wp hooks to set the roles in Auth0. Eg. On register, login, etc

In your second site you just need a similar “get token -> get app_metadata” to check for the appropriate roles you set to determine if they are allowed

We used SSO so that the sessions were aligned

Hope that helps

Rob

Hi,

Thanks for the reply

Yes it is multisite and yes it is network activated because we need single point control / replication of the AS support settings across the network.

We could do the deactivations of plugins but most plugins that are installed are critical…so if we need them and AS isn’t playing nice, do we uninstall or might there be a code mod we can do to suppress the errors?

Thanks

Rob

Thanks for the super quick reply!

A couple of things and clarifications:

1.) I was just thinking for via admin side for permissioned agents/admins – not via user reply
2.) The plugin has built in security and yes the users are super trusted
3.) A use case would be embedding a Gravity Forms questionnaire directly into the reply for common problems/resolutions

Is the best way to address this via a custom field and code where custom field would take a text input and we then call do_shortcode after validation and pass it that text?

Thanks