OPSS- Application Stripe Problem 401 Message Received On Browser Window (Doc ID 1348197.1)

Last updated on MAY 30, 2013

Applies to:

Oracle Platform Security for Java - Version All and later
Information in this document applies to any platform.

Symptoms

 

Facing issues with JPSFilter initialization parameter 'application.name'

It was observed that it was setting the 'application.name' to 'TestWeb', this parameter does not become the application stripe in system-jazn-data.Because of this whenever it was trying to access a protected resource in that application. 401 message error is reported in the browser window.


After removing the 'application.name' parameter all together and redeploy, the authorization checks start working again.
It is need it to know if this is working as designed

<filter>
<filter-name>JpsFilter</filter-name>
<filter-class>oracle.security.jps.ee.http.JpsFilter</filter-class>
<init-param>
<param-name>application.name</param-name>
<param-value>TestWeb</param-value>
</init-param>

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms