Skip to main content
elisabethf82215657
Inspiring
December 14, 2023
Answered

Coldfusion 2023 and SAML

  • December 14, 2023
  • 2 replies
  • 1661 views

I am developing SAML SSO with Azure AD and our Coldfusion application at the moment and in Coldfusion 2021 everything seems to work. The configuration is there and the authentication works as well.

 

When I try to configure SAML in Coldfusion 2023, errors are thrown in spconfig.cfm

 

When I generate a new service provider, the configuration is created but this error is thrown:

Variable GENERATESUCCESSMSG is undefined.

The error occurred in spconfig.cfm: line 122
Called from spconfig.cfm: line 100
Called from spconfig.cfm: line 40
Called from spconfig.cfm: line 1

 

Identical errors (only with other variables) come when deleting / updating a configuration.
Also identity provider creation throws errors.

 

Did anybody experience this?

 

We use Coldfusion 2023.0.06.330617

and SAML package 2023.0.05.330608

 

If I ignore the errors thrown and try to init SAML authentication also an error is thrown (that may be because the configuration is not correct):

 

java.lang.NullPointerException: Cannot invoke "String.toLowerCase()" because the return value of "coldfusion.runtime.ApplicationScope.getApplicationPath()" is null
body: at coldfusion.saml.SamlHelper.getStructFromAppScope(SamlHelper.java:472)
body: at coldfusion.saml.SamlRequestBuilder.getIdp(SamlRequestBuilder.java:374)
body: at coldfusion.saml.SamlRequestBuilder.initAuthRequest(SamlRequestBuilder.java:149)
body: at coldfusion.saml.SAMLServiceImpl.InitSAMLAuthRequest(SAMLServiceImpl.java:577)
body: at coldfusion.runtime.CFPage.InitSAMLAuthRequest(CFPage.java:17693)

 

Can anybody help?

 

    Correct answer Charlie Arehart

    Elisabeth, yes someone else has reported this. See:

    https://tracker.adobe.com/#/view/CF-4219674 

    which indicates Adobe has a fix, though it's not clear what update will include it. See my comments at that tracker ticket, and add a vote to be notified when Adobe may respond with clarification about how you can get that fix now. 

    2 replies

    elisabethf82215657
    Inspiring
    December 14, 2023

    Now the SAML authentication works even while the configuration still throws these errors.
    So I will wait until the issue is fixed in one of the next updates (hopefully).

    Charlie Arehart
    Brainiac
    December 14, 2023

    That's very interesting that it was not working before but is now. It could be interesting to understand when it "fails" and when it does not. But sure, if they fix it at least the error msg will go away.

    /Charlie (troubleshooter, carehart. org)
    Charlie Arehart
    Charlie ArehartCorrect answer
    Brainiac
    December 14, 2023

    Elisabeth, yes someone else has reported this. See:

    https://tracker.adobe.com/#/view/CF-4219674 

    which indicates Adobe has a fix, though it's not clear what update will include it. See my comments at that tracker ticket, and add a vote to be notified when Adobe may respond with clarification about how you can get that fix now. 

    /Charlie (troubleshooter, carehart. org)
    elisabethf82215657
    Inspiring
    December 14, 2023

    Thanks a lot, Charlie! I did not find this!