IBM Support

PI89363: PROTECTEDVIEWEXCEPTION FOR A PROTECTEDVIEW ACCESS WHILE CHECKING THE ORIGINHEADER FOR APPCONTEXTPATH

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • ProtectedViewException for a protectedview access while
    checking the OriginHeader for appContextPath
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server Liberty    *
    *                  and Traditional Profile users of JavaServer *
    *                  Faces (JSF) Apache MyFaces 2.2              *
    ****************************************************************
    * PROBLEM DESCRIPTION: JSF 2.2 throws a ProtectedViewException *
    *                      when the Origin header is passed in the *
    *                      request                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Some browsers add the Origin header to the same origin requests.
    When that happens, JSF throws a ProtectedViewException.
    
    The ProtectedViewException will look similar to the following
    snippet:
    
    Caused by: javax.faces.application.ProtectedViewException
    	at
    org.apache.myfaces.lifecycle.RestoreViewExecutor.checkViewProtec
    tion(RestoreViewExecutor.java:399)
    	at
    org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(Restore
    ViewExecutor.java:280)
    	at
    org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(Lifecycl
    eImpl.java:196)
    	at
    org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl
    .java:143)
    

Problem conclusion

  • The JSF MyFaces 2.2 code was updated to not check the Origin app
    context path.
    For more information and fix details, see:
    https://issues.apache.org/jira/browse/MYFACES-4058
    
    The fix is enabled by default with the following context
    parameter set to false:
    org.apache.myfaces.STRICT_JSF_2_ORIGIN_HEADER_APP_PATH (true /
    false - default)
    
    The fix for this APAR is currently targeted for inclusion in
    WebSphere Application Server Liberty Profile fixpack 17.0.0.4
    and WebSphere Application Server Traditional Profile fixpack
    9.0.0.6. Please refer to the Recommended Updates page for
    delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI89363

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    CD0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-10-25

  • Closed date

    2017-11-06

  • Last modified date

    2017-11-06

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    LIBERTY PROFILE

  • Fixed component ID

    5724J0814

Applicable component levels

  • RCD0 PSY

       UP



Document information

More support for: WebSphere Application Server

Software version: CD0

Reference #: PI89363

Modified date: 06 November 2017


Translate this page: