Now, I’m not used to study these documents. But today I browsed through them and one thing caught my eye.
I did some implementations of Weblogic as a SAML2 Service Provider against MS ADFS. I’m even invited to do a talk ‘SSO with ADFS for Apex Using Weblogic and ORDS: How I did it and Where I Tripped‘ at the UKOUG Southern Technology Summit 2019, july 2nd.
What’s interesting here is that about 2 years ago I already wrote about my earlier experiences, and mentioned that Weblogic 12c did not support SHA-256 for the signing of SAML requests. So you had to configure ADFS to use SHA-1. In my latest implementation it stroke me that I did not have to force my ADFS counterpart to set that, at least I think I didn’t. ADFS as you might expect for really some time now, uses SHA2 (SHA-256) as a default. But only today I saw that under Manageability Improvements -> Security is mentioned that Weblogic 184.108.40.206 also has SHA2 as a default now.
Knowing this will improve my talk greatly. I’m glad I saw this. It might seem to be a minor thing, but I think it’s quite important. Read the complete article here.
For regular information become a member in the Developer Partner Community please register here.