Access Control In GlassFish 2.1.x Blocks All Access
(Doc ID 2083658.1)
Last updated on JUNE 08, 2022
Applies to:
Oracle GlassFish Server - Version 2.1.1 to 2.1.1 [Release 2.1]Information in this document applies to any platform.
Symptoms
NOTE:Names used; eg test, test1, test21 etc other used represent fictitious names are made up as examples.
Any similarity to actual code, is purely coincidental and not intended in any other manner.
---------------------
Attempting to restrict access via hostname blocks all access to GlassFish Server. For example, if the following is defined in the "testing" configuration for the virtual server called "test":
$ ./asadmin set testing.http-service.virtual-server.test.property.allowRemoteHost=test1.<DOMAIN_NAME>
$ ./asadmin set testing.http-service.virtual-server.test.property.denyRemoteHost=test2.<DOMAIN_NAME>
Updates domain.xml with:
<http-service>
<virtual-server id="test" network-listeners="http-listener-1,http-listener-2">
<property name="allowRemoteHost" value="test1.<DOMAIN_NAME>"></property>
<property name="denyRemoteHost" value="test2.<DOMAIN_NAME>"></property>
</virtual-server>
</http-service>
Both hosts will be denied access.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |