Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

NameIDType.ENCRYPTED cannot be resolved

Written By

Dávid Hegedüs

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • You might run into the following error after deploying SAML in Liferay Portal 6.2 on a Weblogic:
    identity_provider.jsp:53:106: NameIDType.ENCRYPTED cannot be resolved
<aui:option label="encrypted" selected="<%= nameIdFormat.equals(NameIDType.ENCRYPTED) %>" value="<%= NameIDType.ENCRYPTED %>" />
  • This is a bug with Oracle in regard to NameIDType.ENCRYPTED not being resolved in Weblogic 10.3.6. The "Weblogic 10.3.6 internal JSP compiler uses bad classpath for JSP compilation" bug is found at https://support.oracle.com/epmos/faces/ui/km/BugDisplay.jspx?id=17895529 , but unfortunately not visible for simple Oracle accounts without Support Identifier.

Environment

  • Liferay Portal 6.2

Resolution

  • The suggested workaround from Oracle is to upgrade to Weblogic 12c.
  • Another workaround can be setting <prefer-web-inf-classes>true</prefer-web-inf-classes> in weblogic.xml, either in the already deployed portlet where the file already exit or creating the file in the plugin war to be deployed.

 

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?