Let’s assume that we have two websites, mentioned in your question – abc.com, xyz.abc.com, and their table prefixes are – ab_, xy_. Requirements Both websites must be installed within the same domain. Both websites must share the same database using different table prefixes. Both websites must share user tables ( ex. ab_users, ab_usermeta ). Websites’ … Read more
I think this should definitely be doable. I think I would first try to get one of the LDAP authentication plugins — like Simple LDAP Login or LDAP Login Password and Role Manager — working, and then write a small custom plugin to handle the content authorization. Here’s a rough outline of the custom plugin’s … Read more
The way I think this needs to be done: Examine how an existing integration allows a particular CMS to authenticate using wordpress. Possibly this MediaWiki integration. Work out how this authenticates a wordpress user. Examine an existing friendica authentication plugin, such as the LDAP one that comes with the CMS, and update this to use … Read more
A recent comment brought my attention to this question, which I had posted. I had also posted another question regarding this topic, and had later solved it and posted an answer, here: JWT authentication with WP – Approach Copying that answer here, so that it helps someone who stumbles across this implementation: The endpoint coded … Read more
In WordPress Admin Enable the JanRain Engage plugin Go to Settings > Janrain Engage and enter your Engage API Key (which you can find on your Janrain dashboard under API Key). Turn on self-registration. On the Janrain Dashboard Add your WordPress domain under the Your Domains section. Go to Sign-in and select the Choose Providers … Read more
Here’s one milder suggestion to try out, assuming different cookie domains, if you’re using WordPress 5.5+ For your development installs, set the getenv environment variable WP_ENVIRONMENT_TYPE or define: define( ‘WP_ENVIRONMENT_TYPE’, ‘development’ ); within the corresponding wp-config-development.php or the name you use for it. Then extend the authentication cookie expiration period for the development installs with … Read more
This showed up as a notification due to the upvote. Here’s how I solved it. The endpoint coded in the app that I am supposed to authenticate with prepares the token. The token has to be in the specified format. It then should be base 64 encoded and hash encrypted. The wp_init handler should be … Read more
Cross-site Scripting Issues You cannot transfer WP auth cookies between domains. You also don’t want to store plaintext passwords for logging into another WP installation programmatically. So, you’ll have to have users log into WordPress, and then access their login status via an API endpoint from the third-party site. This lets WordPress handle all the … Read more
OK, the approach that’s working for me is as follows: Assume that the main site user database is authoritative. The main site login cookie contains an ID and a hash of the site password. Get the cookie from the main site and revalidate it against the main site’s authentication API If valid, use the email … Read more
I have installed “WP Cassify” plugin to enable CAS login for my WordPress.But after entering the username and password in CAS login screen, I am getting following error in my web browser: Error [ wp_cassify_do_ssl_web_request ] : SSL certificate problem: self signed certificate I don’t know the reason behind this issue. I am using ubuntu … Read more