Hi! Excellent plugin.

How do I send a page to public or private access when I create it.

All pages I create send it to private. I mean, when I create it, without enter in the plugin settings and send it to public part.

Thank you

We got locked out of our WordPress instance this weekend. We did not realize that our Client Secret had expired, so the Oauth2 option we had set up stopped work. Just got a blank white screen. We then tried access by using https://www.oursite.com/wp-login.php?external=wordpress but that also failed. We resolved by uninstalling the plugin. Logging into WordPress, then re-installing the plugin while still having an active WordPress session. That allowed us to enter a new Client Secret and get the Oauth2 option back working. On our end, we need to find a way to track Client Secret expirations. But there might be a bug that prevents wp-login.php?external=wordpress from working in this type of scenario.

After the update to 3.10.2 I can’t login with OAuth2 anymore (WordPress says “There has been a critical error on this website”). Still can login with CAS, but we need it to work with OAuth2.

It was working yesterday afternoon, then Authorizer got updated during the night and OAuth2 is no longer working today.

I tried with both my development and my production servers and they do the same. Both run with WordPress 6.6.2.

Please help!

Our site ends up error “HTTP redirect status code must be a redirection code, 3xx” after the Authorizer automatically updated.

We have to restore the site from the backup and stop the auto update for Authorizer. We have tested manually updating the Authorizer to the latest version 3.10.1 and it brought down the site immediately after. And same error happened when accessing the site, so it confirmed the issue from the update of Authorizer.

Aloha! I am attempting to use the Authorizer plugin on an existing multisite installation and have run into some problems during the initial activation of the plugin. We noticed that the plugin doesn’t always add the existing users of a site within a multisite network to the approved users table. (On some sites in the network, it appears that the function ran correctly. But in other places it was never run. Or, at least it did in our specific hosting environment.)

Two questions:
1) Is there a setting that I missed that would guarantee this to happen? If so, is the best course of action to uninstall and possibly reinstall the plugin with that option set properly?
2) Is there a DB option (or options?) that I can update manually with WP-CLI that stores users in the approved users list?

Appreciate the response. The plugin is fantastic!

I’ve enabled this plugin (using CAS logins) at the multisite level. Works great.

But I want to be able to set the individual sites to have different default users (while maintaining the CAS settings). When I go to uncheck the “Override individual site settings with the settings below” option, I can no l longer save the settings. Everything just grays out.

Do I have to enable the plugin on each individual site to get this to work?

The question is actually quite simple, but I haven’t found a direction yet. Users in the LDAP domain we have are @abc.com emails and I need those emails to be “transformed” to @xyz.com after a successfull authentication.The closest I found was using functions.php but without success.

It seems I have to create a hook/filter do make that transformation, but don’t really know how to go from here.

Hi

I need to provide a scope (openid email profile) for our OIDC, but can′t find the field for it.
Did I miss something? Or do you have a workaround, maybe with a filter or other function?

Hi,

We have a custom plugin that calls the Authorizer ‘authorizer_user_register’ hook, and uses the returned user data to assign WordPress roles to users based on their membership in Active Directory groups. This worked well in the past, but now the do_action for this hook is never called, and I have no idea why. Is this the only way to get that user data from Authorizer?

Authorizer: 3.9.0
WordPress: 6.5.5

Regards,

Mark

• This topic was modified 3 months, 4 weeks ago by mpemburn.

Aloha! We currently use this amazing plugin on a site that we’re moving into Pantheon. For our SSO, we’re using OAuth2 with Microsoft Azure.

The issue we realized we’ll run into is that we will have different Client IDs and Client Secrets for dev, test, and prod on Pantheon. If we ever copy the prod database to test and dev, the test and dev Client IDs and Secrets will be incorrect for those sites, so SSO will break until we fix them manually.

I see that there is a way to define AUTHORIZER_OAUTH2_CLIENT_SECRET in wp-config, which we could do in Pantheon programmatically based on environment, but I don’t see a way in Authorizer to define the Client ID in wp-config (something like AUTHORIZER_OAUTH2_CLIENT_ID).

Is the Client ID something that also could be added as an option to be defined in wp-config?

Aloha Paul! ??

Hope this finds you well. Thank you so much for your previous help with storing credentials in wp-config.php!

Now I’m testing PHP8, but facing this error: Usage of ldap_connect with two arguments is deprecated. I believe it comes from class-authentication.php:1095

$ldap = ldap_connect( $ldap_host, $ldap_port );

Now quick and dirty fix would be just to remove the port, which will probably work for me at this time, but it’s always better when fix comes from the Developer. Might I suggest something in terms of this?

// If a scheme is in the LDAP host, use full LDAP URI instead of just hostname.
if ( array_key_exists( 'scheme', $parsed_host ) ) {
// If the port isn't in the LDAP URI, use the one in the LDAP port field.
if ( ! array_key_exists( 'port', $parsed_host ) ) {
$parsed_host['port'] = $ldap_port;
}
$ldap_host = Helper::build_url( $parsed_host );
} else {
$ldap_host = 'ldap://' . $ldap_host . ':' . $ldap_port;
}

// Create LDAP connection.
$ldap = ldap_connect( $ldap_host );

TLDR: Look for a space at the beginning of your Google Client ID in the Authorizer Settings.

I suspect there are various reasons for the *white screen* issue. I’m just sharing my resolution in case it may help someone.

Examining the URL for my “white screen”, URL was: (Note: BOLD)

https://accounts.google.com/v3/signin/identifier?continue=https%208744...

The %20 is a space in front of the Google Client ID. I removed the space and the *white screen* is gone.

The developers may want to trim this field before it gets saved to avoid this problem.

I got rid of the space and it’s working! I’m very excited to use this plugin.

Hi,

We’ve been experiencing website crashes daily (Internal Error 500 [nginx]), and I believe I’ve identified the cause as numerous calls to Options:set_default_options(). To test this, I added return statement to the first line of that method, and the page response time has improved significantly. Is it possible for you to limit the number of times this method is called?

For reference:
Authorizer 3.8.3
WordPress 6.5.5
Multisite with 192 subsites

Regards,
Mark Pemburn
Clark University

Hello,

I’m building a site using Themeco’s X theme and the Cornerstone page builder plugin and I noticed that the builder doesn’t work when I have Authorizer activated. We need this activated to have the entirety of the site automatically redirect to a CAS login portal. My random guess here is that there’s something going on with getting the builder to load on the domain despite Authorizer forcing each page to a CAS login on the frontend, but I really don’t know. Is there a way around this to allow Cornerstone to work while keeping all the same Authorizer settings? I’ve tried allowing just the home page as public access, but that didn’t fix it.

Thanks,
George

Hi. I use “Authorizer” version 3.8.1 with LDAP as external service. I have noticed that if add a user in “Access Lists”->”Approved Users” or if I approve a pending user and I set the role to “Administrator”, the first time that the user logins the role is reverted to “Subscriber”. I have to change again the role after the user’s first login.

I think it has something to do when it creates the user in wordpress.

I have read https://www.ads-software.com/support/topic/administrator-users-revert-to-subscriber/ but it’s not my case.

Thanks in advance for your help.

Hi, I was working with Event Calendar and we ran into a roadblock. Wondering if there is a possibility of manually enter a particular site to make it public,

currently the issue is authorizer is making the view change option on the site broken.

{
“code”: “rest_cannot_view”,
“message”: “Notice: You are browsing this site anonymously, and only have access to a portion of its content.”,
“data”: {
“status”: 401
}
}

Their solution is needing this specific URL accessible to the public
https://website.com/wp-json/tribe/?

Thank you

Hi,

We use Authorizer for our main websites so that we can log in via ADFS. Recently, we created a new site that can only be accessed by users in our domain (clarku.edu). I’ve assigned the Administrator role to a handful of people, but when they log in, Authorizer reverts them to Subscriber. Is there a setting to prevent this from happening?

Thanks!

Mark Pemburn
Web Application Administrator
Clark University

Authorizer seems to be using an enormous amount of memory to render its admin pages on a very large multisite network (~6 GB database, 103 sub-sites) we host. Where most admin pages on this particular site usually take around 30 MB of RAM to load, Authorizer takes over 100 MB on the Network dashboard, and over 180 MB on the base site and a few sub-sites. Other sub-sites come in closer to 100 MB. I actually had to increase the PHP memory limit to get the admin pages to load on some of the sub-sites, since we’re otherwise allowing a maximum of 128 MB (and I can’t increase that limit in production).

This occurs with both Authorizer 3.6.3.1 and 3.7.1. I’ve tried eliminating other heavyweight plugins without impact. This seems to just be Authorizer using 70-150 MB of RAM to render its admin pages on this site, whereas on smaller sites it seems to only consume 2 MB or so.

Do you have any suggestions?

An odd and inconsistent bug is causing apparent login failures for certain users (but the login actually succeeds, in the background). 

Using the CAS Logins component of Authorizer (v3.7.1, on WP v6.5.2), most users log in without problem. But for a few users, the CAS login steps work fine, but then the screen hangs for ~2 minutes before eventually timing out with a 502 Bad Gateway error from Cloudflare, having never reached the WP dashboard. But what’s particularly puzzling is that if that user navigates back to the WP site from the error page, it turns out they ARE logged into WP, with the WP admin toolbar at the top of the public site, and virtually all of the admin side accessible. The one page that consistently won’t load, even from within the WP admin, is the default dashboard (/wp-admin/index.php or just /wp-admin/).

Any suggestions for troubleshooting steps to figure out what’s going wrong here?

~ Steve McConnell,  UC Berkeley

In our production environment, when users login during a fresh browser session, they get a blank screen. The admin dashboard will load, but only after refreshing the page 5-10 times. We think it might be caching related since it only appears to be an issue on our prod environment. We using Pantheon as our hosting provider and in prod they add caching services that don’t appear to be present in the dev and test environments. At least that’s one angel we thought we should ask about. It has been happening for a while and we haven’t been able to figure a solution beyond continuous refreshing of the browser.

For SSO, we are using Microsoft Azure AD/Entra ID SAML authentication from a single source. I don’t believe in this instance there is any load balancing going on.

An example URL we see when a login attempt gets stuck on a blank page is the following (instead of redirecting to /wp-admin):

https://our.site.com/wp-login.php?code=0.ATUAe_M2EFkNnEiogBpq69K9B9z9mnqgE0RGlFCdudvtexo1AAA.AgABBAIAAADnfolhJpSnRYB1SVj-Hgd8AgDs_wUA9P_998thzLE85d8dfya-WLvUjJlITQgMJfyLE9hHxQZC5NxoJTGUAM0EDBqGMHfa_qSLNx6FPDVnnaEL9Gv5NcM45YjosAv8N6aHxFFoYwf63_YuAoaLnf2CcWWldy5dn-pbXEu_QqOGAslVVf7ctU01UdW9KfO0eI6VGLX1AihMOHFDMgFa8iaM6fWR8M91H1ndrk7seYGMwNwoAJCSfbNYg65Juyj5-umC6lJB3Z4zQM3bMIRdq66wOM5qSsK8wQkByaSbdfuEhBFCGjqztryP8h2sLFZ2Deez3JK3nf9G7iiVP8XRzX3_cB1vodt-kBI_TVvAYxY0XtonKzDyXrLsohuprBvHWkjKiavP7Rr5bgDvfkp5v4uqnnb85y9BgTvbgy_HTtytSP3P6mocKNctk-OkpOcB4ZGuFGWNVqAxn6wUmD6Nka8zLS1ODyj1oEuAq8lGKVuIRC71e3qvP7LmKr0TtgCja2pD7DbksDBkOMfRRWukjGMk98eK7k5xn8PoZL6cNBskjeYI1l-gxLtGKqeUSSlQF7BkPEX2WucDG6jF_xpNPLoNeMleZtMgqj5aO1T9O3D1WGuHn3PQgfl5D92R0itdU2FX2wioUrIUrRvdxDHjy3GdHZWJsyDDrlFqSFL7hMTqCREULF-oZ8URxX_zjuGZ7xy2YAi6emYshDjAugF_6yBc_aadidpnsYaIdjgZN3LKM6z9MWOISi27IK85xJAGaSGylM7qahwdbElFwykfaVmOjQY8aF4w-R6nRRDrAj_bCgkXiBaQVdxrasaHXv41a9dLt0rDW0PR&state=29faea0d242a749fe96101fee928a0b4&session_state=3fc0d5b3-95e1-49a8-9ef6-1feee9a5a686#

Any ideas?

Hi,

I am using the authorizer_has_access filter in functions.php to validate that a user is in a list of valid users to access a certain page of my website. If the user is logged in but is not in the list, I set has_access to false in the function that is called for the authorizer_has_access filter. I can see that my function is working correctly (based on printing to screen) in the function to determine whether the user should have access to the page, and it works correctly when has_access is set to true, to continue to show the page, but when has_access is false, I am getting a browser error ERR_TOO_MANY_REDIRECTS. I had thought either the plugin would redirect to a certain page (how do I specify what page?), or it would show an error message that you do not have access to view this page.

Is there another step I need to do to configure what happens when the user is logged in but does not have access to a page? I checked the Authorizer settings for anything like a page to show when access is denied, or a message to show, etc. and don’t see anything.

Thank you,

Colleen

We have noticed that the Authorizer plugin is using an outdated version of the GuzzleHttp library. This is causing conflicts with other plugins and tools we use in our project, as they require a newer version of this library. These dependency conflicts significantly hinder our project maintenance, as we are forced to modify your plugin, which is not an ideal solution.

Is it possible for you to consider updating the GuzzleHttp dependency to its latest version in the upcoming release of the Authorizer plugin?

Hello,
Would it be possible to bypass entirely the WordPress signon screen to get directly to the IdP logon screen for a smoother experience?

db

Hello, I’m trying to make Authorizer work.

Alas, I’m struggling against white page phenomenon.

With the same parameters, MiniOrange OpenId SSO plugins is working but I don’t like Miniorange (too complex, wants to do everything, like μSoft).
I needed to disable an extension, UpdraftPlus, that was using a version 6 for Guzzle.

I don’t have a clue at this time since I cannot catch any errors in any log (wordpress log is not enabled). What I can say is that the container is using PHP8.1, the latest WordPress version is running and that, sometimes, but not always, there are (too) many loops between the IdP and Authorizer.
If you have some ideas where to look for.

Thank you for you product,

db

Would it be possible to add an option to block the forgot password page? Even with “Disable WordPress Logins” checked, it still is accessible. We’ve had a few hacking attack attempts though this method. Since we have SSO configured, and WordPress logins hidden, they cannot get in. Until/unless they know we are using the Authorizer plugin and leverage the external=wordpress option. So far, this does not seem to be the case, but would like to pursue any options to prevent login attacks.

wp-login.php?action=lostpassword

I am having the same problem as described here: https://www.ads-software.com/support/topic/users-being-randomly-demoted-to-subscriber-initial-role/

It’s actually been going on for some time, seemingly at random, but only very occasionally. However, it’s happened twice this week, and I’ve finally noticed a commonality. Both times, the users appear in the logs with a previous permission level AFTER they’ve had a single failed login immediately before. In one case it set someone back to “subscriber” from “editor.” In the second case it set someone back from a higher custom site-specific role (Researcher Admin + Editor) (Members plugin) to a lower one that they had previously held (Researcher).

This happened in two completely separate multisite networks, both of which are using the Authenticator plugin for LDAP logins.

I have LOTS of users who have been assigned non-default roles in our various sites, and typoed passwords are super common, and yet this particular issue doesn’t come up very often.

By any chance do you have any insights for me? I’m happy to work with you as much as I can if you want to dig into it.

• This topic was modified 8 months, 1 week ago by vickifarmer.

Hi,
We use Authorize to integrate with our CAS/ADFS system, and have been experiencing some significant slowdowns in one of our websites that appear to be related to the plugin. Our hosting vendor isolated the problem to this call:

Authorizer\Updates->auth_update_check() | authorizer/src/authorizer/class-updates.php:25

According to their logs, this call took 19 seconds to complete. We’re currently on version 3.6.3.1 and running the latest version of WordPress (6.4.3).

Thanks!
Mark Pemburn
Clark University

I have a number of employees who regularly join and leave my organization, I was wondering if there is some information about how to add or disable users in Authorizer using a script of some sort?

TY in advance.

We use authorizer on a private website and also use the Events Calendar Pro to house our college events on that site. We ran into an issue after the most recent Calendar Update where Authorizer seems to be causing a 403 error for the Calendar and it will not allow users to change views on the calendar or move forward in days/months. We ran through plug in conflict tests to figure out that authorizer was causing the issues. Is there a way to White list the events calendar in Authorizer?

Hello, I work with WordPress 6.2.2, it is a WordPress Multisite with more than 20.000 subsites, authorizer 3.6.3.1 and PHP 8.1. The validation is done by CAS SSO and works correctly, but we detect a seemly random error, where the users don’t get redirected to the login page, we think it may be something wrong configured in the plugin.

After trying several times it redirects to the CAS.