Skip to main content
D
dominic_varillo
Participant
April 15, 2025
Answered

SAML SP

  • April 15, 2025
  • 2 replies
  • 1172 views

Hi,

I am receiving the error message: "The getSpMetadataForAdmin method was not found." when I click on an existing SP to edit it. I also get the message when I add a new SP. It adds the SP but then throws the error when try to display it. Adding and editing an IDP is fine. I am on CF 2021 Standard. I upgraded to update 12 from 5 and changed the JVM to 11.0.26 and uninstalled and reinstalled the SAML package to try to fix this but I still get the error. It seems manually modifying the neo-saml.xml file does not work either without restarting CF, but that is still unclear. Has anyone else experienced this or know how I can fix it?

Thanks,

Dom

Correct answer Charlie Arehart

Folks, there are two different issues being discussed here: while both relate to editing sp configs, Dom's is the error about " getSpMetadataForAdmin method was not found" (happening on his update 12) while Scott's is the "keystorepath" error as he mentioned on his tracker ticket (where he also indicated he is on update 18).

 

1) So first, about Dom's error, I can report that that IS indeed SPECIFICALLY because he is on update 12. I finally had time to set things up and test, and the error happened on 12 but NOT on 13 (or later. FWIW, it also didn't happen on update 2, which is where a fresh install started for me tonight.) So Dom (and anyone else with this first error), consider going to update 13 to solve that. Do beware that update 13 (from March 2024) had other significant changes, especially the one about searchimplicitscopes. See the update 13 technote for more on that, and/or an elaborated post I did at the time with still more.

 

2) Second, as for Scott's error, I will say that I have NOT gotten the eror, regardless of what update I'm on. That's odd that it's happening for you. I concur with BKBK pointing out that the Stax error (you refer to in the tracker ticket) is something EVERYONE sees. You can ignore it, and therefore it's NOT the issue (but I appreciate why you wondered if it may be).

 

I'll propose to you here what I did above to Dom in my FIRST reply (and we can add it to the ticket if it works for you): stop CF, delete the felix-cache folder (in cfusion/bin) then start CF. No need to "save" that folder: the restart of CF will replace the folder for you. And if that alone doesn't work, consider next stopping CF and deleting (or renaming) the cfusion/wwwroot/WEB-INF/cfclasses folder. Then start CF and again it will be created for you.

 

Both those steps simply involve clearing out previously compiled java that may have been implemented in prior updates for you. Again, I don't get the error you do, so it seems definitely something environmental on your end. And since your edit of the neo-saml.xml is not preserved it COULD be related to that issue.

 

Hope these help here.

2 replies

Charlie Arehart
Community Expert
Charlie ArehartCommunity ExpertCorrect answer
Community Expert
April 24, 2025

Folks, there are two different issues being discussed here: while both relate to editing sp configs, Dom's is the error about " getSpMetadataForAdmin method was not found" (happening on his update 12) while Scott's is the "keystorepath" error as he mentioned on his tracker ticket (where he also indicated he is on update 18).

 

1) So first, about Dom's error, I can report that that IS indeed SPECIFICALLY because he is on update 12. I finally had time to set things up and test, and the error happened on 12 but NOT on 13 (or later. FWIW, it also didn't happen on update 2, which is where a fresh install started for me tonight.) So Dom (and anyone else with this first error), consider going to update 13 to solve that. Do beware that update 13 (from March 2024) had other significant changes, especially the one about searchimplicitscopes. See the update 13 technote for more on that, and/or an elaborated post I did at the time with still more.

 

2) Second, as for Scott's error, I will say that I have NOT gotten the eror, regardless of what update I'm on. That's odd that it's happening for you. I concur with BKBK pointing out that the Stax error (you refer to in the tracker ticket) is something EVERYONE sees. You can ignore it, and therefore it's NOT the issue (but I appreciate why you wondered if it may be).

 

I'll propose to you here what I did above to Dom in my FIRST reply (and we can add it to the ticket if it works for you): stop CF, delete the felix-cache folder (in cfusion/bin) then start CF. No need to "save" that folder: the restart of CF will replace the folder for you. And if that alone doesn't work, consider next stopping CF and deleting (or renaming) the cfusion/wwwroot/WEB-INF/cfclasses folder. Then start CF and again it will be created for you.

 

Both those steps simply involve clearing out previously compiled java that may have been implemented in prior updates for you. Again, I don't get the error you do, so it seems definitely something environmental on your end. And since your edit of the neo-saml.xml is not preserved it COULD be related to that issue.

 

Hope these help here.

/Charlie (troubleshooter, carehart. org)
    S
    Scott_Stewart3951
    Known Participant
    April 24, 2025

    I cleared the felix cache, cfclasses, java cache.. even cleared the browser cache. Same result. I did however observe that it seems to be centered around the field for the keystore password, I unchecked sign logout response, saved and the form rendered, however with the data for the fields below missing . When I edited the file again I replaced the missing data, saved and then the form crashed with the same missing keystorepath error

    Its the same fields that are deleted from neo-saml.xml everytime. 
    signKeystorePath
    signKeystorePassword
    signKeyStoreAlias

    Charlie Arehart
    Community Expert
    Charlie ArehartCommunity Expert
    Community Expert
    April 24, 2025

    Would you be willing to share privately the xml file? I'd compare it to a working one. Perhaps there's something amiss, some subtle difference. My email is charlie@carehart.org. 

    /Charlie (troubleshooter, carehart. org)
    Charlie Arehart
    Community Expert
    Charlie ArehartCommunity Expert
    Community Expert
    April 18, 2025

    Here are two things to try:

    1.  Do what the technotes refer to as "clear the felix-cache", by which they mean stop CF, and delete the folder in cfusion/bin called felix-cache (deleeting it and all subfolders, with no need to "save them" for any reason). On restart, CF will rebuild them. Even though it's not a known issue tha tthis would help with your problem, it has helped with many (as indicated in various update technotes over the past few). This folder holds files related to CF's "package management" feature, and it seems that sometimes something gets out of synch, which is why Adobe recommends this "solution".

    2.  If that does not work, then stop CF again and delete the cfusion/wwwroot/WEB-INF/cfclasses folder.  This folder instead holds the java classes compiled from your CFML. Again, sometimes things get out of synch. For this folder, there is an argument for renaming it rather than deleting it (while CF is stopped), as there may be some value in the info tracked about these files.  It shoudn't be "huge" in size. And if you wanted to, you could do both after stopping CF for step 1. I only proposed them separately to help you (and us) know "which"solved it, if either does, for the benefit of future readers.

     

    Let us know if it helps or not. If not, I have another suggestion but I'll hold off to hear what you report.

    /Charlie (troubleshooter, carehart. org)
    D
    dominic_varilloAuthor
    Participant
    April 21, 2025

    Thanks for the reply Charlie. Unfortunately, I did each of these separately and each time I received the same error message when I try to edit the one test SP i have created. Any other suggestions would be appreciated.

    Dom

    S
    Scott_Stewart3951
    Known Participant
    April 23, 2025

    I'm seeing a similar issue, when updating Service Provider configuration data. I hit update and the form crashes. I can shut down the CFApplication service and reconstruct the neo-saml.xml file and then restart, but this is clumsy at best.

    I've opened a bug tracker: https://tracker.adobe.com/#/view/CF-4226362

     

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices