markphipps

Hi Mike,

Using the user capabilities editor, I switched the user to administrator, then logged in as her. Then I opened up the Job Data view. I then switched the user back to author and had her re-login and the Job Data view still showed for her.

I’m wondering if somehow her capabilities were corrupted.

Anyways, it is working now.

Thank you for your help!
Mark

I’ll try asking the user to disable any extensions that are active. It does work for me, but not for her.

The only other thing I could think of is the French IE11 versus the English IE11. I’ll do some more digging.

Try disabling the iThemes Security plugin through the wp_options table, row active_plugins.

I believe I read it somewhere, but I cannot find the source.

I had heard it was supposed to be fixed in 3.9 .

Cheers,
Mark

As a test, I’ve made a copy of the website and updated it to 3.8.2. I’ll see if the cron runs tonight.

It only ran once. When I checked today(April 14), it said the next scheduled run was April 7th. I am running this under 3.6.1 – would this be the issue?

1.8.2 – it looks like the cron ran for the first time yesterday. I’ll keep any eye on it and see if it continues to run.

Hi Mike,

My jobs seem to not be doing that. Is there something missing from my installation?

Cheers,
Mark

What do you mean by ‘expired’ status? I don’t see an expired flag in the job details.

btw, in your array below, is one of those entries suppose to contain your username? I would have thought that the username was something like ‘nkumar’?

Hi Nithin,

From what I see above, the PING server isn’t sending the username information at all. Perhaps the field being mapped is empty?

Is this link of any help at all? The section at the very bottom deals with NameID: https://technet.microsoft.com/en-us/library/adfs2-federation-with-ping-identity-ping-federate(v=ws.10).aspx

This also looks related for PING: https://www.pingidentity.com/support/solutions/index.cfm/PingOne-Error-in-Single-Sign-On-SAML-210-Missing-NameID-when-using-ADFS-as-the-IdP

Hope this helps,
Mark

Hi Nithin,

I’ve never seen this error before. From backtrace line 2, it looks like it can’t find the current binding — double check the name/url of your endpoint.

Hope this helps,
Mark

Hi Nithin,

No idea with PING at all, but I expect it will work in a similar way. Find your attribute store and see what claim is being sent for username? Perhaps the username is being sent under a different variable name to the SAML plugin.

Hope this helps,
Mark

Good afternoon Nithin,

The two above entries need to be made in the ADFS 2.0 management console
-> trust relationships -> relaying party trusts -> (pick one) -> edit claim rules.

Hope this helps,
Mark