I believe I did see something like this.  I was chasing a different investigation and did not spend the time trying to dig deeper or determine whether it was an expected condition.  I too just backed off to the previous Advanced Authentication client version.

What I recall from the LAN trace is that it was suggesting the failure was TLS-related, as though with the later client wanted either a TLS version or a cipher suite that the server could not satisfy.  So you might want to look at it from that perspective, to confirm or rule out.  Don't know if the later client perhaps needs a particular AAF server version or policy in order to be satisfied.

Well here's the thing.  Aauth client 6.4.2 standalone on workstation without oes client worked in my tests.  I do know 6.4.2 requires tls 1.3 by default, but this is provided by aauth server so not issue. 

Oes client as far as I'm aware just hands off to aauth client, then baton passes back to oes when that workflow is complete, so it's a little confusing.

I have an Sr open so we'll see where that goes 

UPDATED:   support confirmed it's a known issue now and has been escalated

Oh come on. Surely this should have been tested by both the AA and OES teams prior to release? Please let us know when you get a fix.

There's a temp workaround, but the proper fix from OES client side has been bumped to 2025.
There's requests to escalate this.  Open SR and reference OCTUS52A868027, and https://portal.microfocus.com/s/article/KM000024652

Maybe with some pushing we can get some resources put on it asap.

I will open SR for it.

When you get the number for the SR, please could you post it so that we can quote it when the rest of us ask?! I want to build a new combined installer for use over the student vacation.

Tom

My case # is 02724526