Try to update SAML module to V2.1.2 or latest version and check in the backup application.
Did you clean your userlib folder? Because the new module changes a lot of JAR files in the userlib so you might end up with (a lot) of double or obsolete JAR files that needs to be cleaned out. Do also note that the latest module can have issues with AzureAD and Okta setups. See the forum post here: https://forum.mendix.com/link/questions/107477
Not sure if the SAML version 1.15.4 supports OKTA.
The error “Assertion Conditions are not met” may be due to an actual mismatch between your app's entity ID (The URI configured under "SP Configuration") and the one that Okta is asserting as the Audience URI.
As far as I can tell, previous versions of the SAML module did not check that the Audience URI matches the SP Id, so if there always was a mismatch in the configuration, it would not have surfaced before upgrading to one of the newer SAML modules.