Using wildcards in RDBMSRealm

Question

Hello.
I'm using WLS 5.1 with SP6 running on JDK1.2.2, platform is Windows NT
Server 4.0 SP6.
I want to know if there is a way to use wildcards to create entries for
RDBMSRealm.
The reason I want to use wildcards is that if I create an entry in the
ACLENTRIES table like this...:
A_NAME : weblogic.url
A_PRINCIPAL : testuser
A_PERMISSION : /index.html
I can restrict access for the URL http://localhost:7001/index.html to
"testuser."
However, when I create this entry, weblogic prompts for a username even if I
access a URL other than http://localhost:7001/index.html, for example,
http://localhost:7001/test.html.
When this happens, I cannot access "test.html" by using any of the usernames
that I have listed in my RDBMSRealm USERS table.
I was thinking that this works like the "weblogicURL.policy" file.
If you create one entry in the "weblogicURL.policy" file, all other URL
defaults to "everyone deny access".
I remembered that you can use wildcards in the "weblogicURL.policy" file, so
I tried changing the A_PERMISSION column to the following six patterns...:
A_PERMISSION : *
A_PERMISSION : -
A_PERMISSION : *.html
A_PERMISSION : /*
A_PERMISSION : /-
A_PERMISSION : /*.html
Using the six patterns, I tried to access http://localhost:7001/test.html
each time.
However, none of the four patterns above seemed to work, since I was
prompted and couldn't access even if I tried every username that I have in
my RDBMSRealm, in all of the six cases.
If I cannot use wildcards, this means that I would have to create entries
for every single HTML pages. (probably JSP pages, too)
Is there a way to use wildcards in the RDBMSRealm so that I can simplify
this?
Thanks ahead of time.
RYotaro.

Answer 1

Thanks, Terry and Kishore!
I guess it's not a very smart idea to restrict access on URLs using the
RDBMSRealm...
What I was thinking was that if it was possible to put entries for Servlets,
URLs, etc... into one place, it would be easier for managers to manage
access control.
# For instance, it could cause some people confusion if access control for
URLs are listed in weblogicURL.policy and servlets are listed in RDBMSRealm.
It would be better if all of the entries are written in one place.
As a matter of fact, I have tried web-applications some time ago, and am
thinking of going back to it.
# As I recall, web-applications cannot be "hot-deployed." But there's
probably a way to get around it.
Thanks again!
Ryotaro.
"Kishore Talari" <[email protected]> wrote in message
news:[email protected]...
>
Try using a web application! Servlet spec 2.2+, WLS 510, SP6.
You can do a world of URL patterns!
The only change you will have to make is package the jsp/html,etc pagesinto a .war archive and write a web.xml file.
>
"Terry" <[email protected]> wrote:
I'm not sure that this is the way you want to go about it.
AFAICR there is no need to add aclentries in the RDBMSRealm database when
using the weblogicURL.policy file - simply add an entry to the policy
file
allowing access to all urls for all users, then add more specific entries
for those urls you wish to restrict access to. Adding stuff to the
ACLENTRIES table will not have any effect (I know because that is what I
tried first).
The documentation on wublogicURL.properties should tell you all that you
need to know
terry
Ryotaro Toda <[email protected]> wrote in message
news:[email protected]...
Hello.
I'm using WLS 5.1 with SP6 running on JDK1.2.2, platform is Windows NT
Server 4.0 SP6.
I want to know if there is a way to use wildcards to create entries for
RDBMSRealm.
The reason I want to use wildcards is that if I create an entry in the
ACLENTRIES table like this...:
A_NAME : weblogic.url
A_PRINCIPAL : testuser
A_PERMISSION : /index.html
I can restrict access for the URL http://localhost:7001/index.html to
"testuser."
However, when I create this entry, weblogic prompts for a username even
if
I
access a URL other than http://localhost:7001/index.html, for example,
http://localhost:7001/test.html.
When this happens, I cannot access "test.html" by using any of theusernames
that I have listed in my RDBMSRealm USERS table.
I was thinking that this works like the "weblogicURL.policy" file.
If you create one entry in the "weblogicURL.policy" file, all other URL
defaults to "everyone deny access".
I remembered that you can use wildcards in the "weblogicURL.policy"
file,
so
I tried changing the A_PERMISSION column to the following six
patterns...:
>>>
A_PERMISSION : *
A_PERMISSION : -
A_PERMISSION : *.html
A_PERMISSION : /*
A_PERMISSION : /-
A_PERMISSION : /*.html
Using the six patterns, I tried to accesshttp://localhost:7001/test.html
each time.
However, none of the four patterns above seemed to work, since I was
prompted and couldn't access even if I tried every username that I havein
my RDBMSRealm, in all of the six cases.
If I cannot use wildcards, this means that I would have to createentries
for every single HTML pages. (probably JSP pages, too)
Is there a way to use wildcards in the RDBMSRealm so that I cansimplify
this?
Thanks ahead of time.
RYotaro.