Forum Replies Created

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Contributor Anais Pantheor

    (@anaispantheor)

    Hello @meenasekar,

    Thank you for the report! We are looking into this now and will work on a fix if any adjustments are needed in the plugin code.

    We appreciate your patience while we get this sorted.

    Plugin Contributor Anais Pantheor

    (@anaispantheor)

    @sentrypress, find this excerpt from the readme.txt about installing the filter.

    Where to add configuration code: When using the filter-based configuration approach, add your code to a location that loads before the plugin initializes. You can create a custom must-use plugin or add the code to your theme’s functions.php file (note: theme-based configuration will need to be migrated if you switch themes).

    Plugin Contributor Anais Pantheor

    (@anaispantheor)

    Hi @sentrypress, thank you for the update.
    Would you mind first confirming that you have added the following filter? Without it set up, the problem will persist.

    readme.txt
    If you’re using the OneLogin connection type and need to modify the internal_config (e.g. to set requestedAuthnContext to false), you can use the wp_saml_auth_internal_config filter:

    /**
     * Modify the OneLogin SAML configuration.
     */
    add_filter( 'wp_saml_auth_internal_config', function( $config ) {
        $config['security'] = array(
            'requestedAuthnContext' => false,
        );
        return $config;
    } );

    Hopefully, this should be enough to fix the sso error.

    Plugin Contributor Anais Pantheor

    (@anaispantheor)

    Hi @shonu, it looks like you have missing values in your configuration:
    idp_entityId_not_found
    idp_sso_not_found
    idp_cert_or_fingerprint_not_found

    Were they setup along with the other values?

    Plugin Contributor Anais Pantheor

    (@anaispantheor)

    Hi @shonu,
    The functions wpsa_filter_option and wp_saml_auth_internal_config should be added to a custom mu-plugin (must-use plugin) to prevent them from being overwritten during updates. Alternatively, you can add these filters to your theme’s functions.php file, though they would also be at risk of being overwritten if the theme updates. While they could be added directly to our plugin files, they would be lost during our next plugin update.

    The connection type is a matter of preference:

    • OneLogin: This library is bundled with the plugin, configured via WordPress filters or the Settings page. This is the recommended one.
    • SimpleSAMLphp: Requires a separate Composer installation and manual configuration files.

    In your case, the RequestAuth issue can be resolved by adding the wp_saml_auth_internal_config filter to a mu-plugin (or similar). Just ensure it loads before our plugin to take full effect. This filter only works when connection_type is set to ‘internal’.

    I apologize for any confusion, and I hope I’m not over-explaining or missing your point. We have updated the README to clarify these configuration steps. If you have any further questions, please let us know!

    Example: Create /wp-content/mu-plugins/wp-saml-auth-config.php with:

    <?php
    // Set connection type to internal (bundled OneLogin library)
    add_filter( 'wp_saml_auth_option', function( $value, $option_name ) {
    if ( 'connection_type' === $option_name ) {
    return 'internal';
    }
    return $value;
    }, 10, 2 );

    // Fix Azure AD requestedAuthnContext issue
    add_filter( 'wp_saml_auth_internal_config', function( $config ) {
    $config['security']['requestedAuthnContext'] = false;
    return $config;
    } );

    Plugin Contributor Anais Pantheor

    (@anaispantheor)

    Hi @shonu, the plugin update may have overwritten your configuration.
    If the change was made directly in /wp-saml-auth.php, then the above configuration got updated.
    You definitely need to double check your existing configurations, wherever they were updated that: 'connection_type' => 'internal'
    If not, please update.

    Also, please check your requestedAuthnContext filter, it should look like this:
    add_filter( 'wp_saml_auth_internal_config', function( $config ) {
    $config['security']['requestedAuthnContext'] = false;
    return $config;
    } );

    The added fix mentioned above should fix the requestedAuthnContext issue overall.

    Let us know how it goes.


    Plugin Contributor Anais Pantheor

    (@anaispantheor)

    Hi @shonu, @tekfused, the new release is addressing this issue as mentioned above.
    Let us know if this improves your experience with the plugin.

    Plugin Contributor Anais Pantheor

    (@anaispantheor)

    Hi @tekfused, as replied in a similar topic here: https://wordpress.org/support/topic/simplesamlphp-base-directory-missing-error/, the new release should remove this error log.
    Let us know if you encounter any unexpected error logs.

    Plugin Contributor Anais Pantheor

    (@anaispantheor)

    Hi @meenasekar, the update has just been released. The log should be gone now. Let us know if anything arises.

    Plugin Contributor Anais Pantheor

    (@anaispantheor)

    Hello @sentrypress, the update has been released. Please let us know if this improve your experience with the plugin.

    Plugin Contributor Anais Pantheor

    (@anaispantheor)

    Hello, we will be releasing it in the next few days. Thank you for your patience.

Viewing 11 replies - 1 through 11 (of 11 total)