File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Websphere and the fly likes WAS 3.5.3 Local OS Security Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Websphere
Bookmark "WAS 3.5.3 Local OS Security" Watch "WAS 3.5.3 Local OS Security" New topic
Author

WAS 3.5.3 Local OS Security

Krithika Venugopal
Greenhorn

Joined: Jun 14, 2001
Posts: 15
Hi,
I have configured OS as my authentication mechanism. I am facing the following problem. I have installed WAS in my machine (Windows NT Server).
When I do 'configure security permission' and try to choose 'Selection' and type '*' in the Search field and click on Search, the following happens,
1. The admin console hangs. This happens if I have logged onto my company's domain.
2. No users are listed. This happens if i log on to my machine.
Can anyone explain why this happens? The Local OS is the domain OS or the machine's OS? I am unable to proceed beyond. What should I do to see all the users of my machine?
Regards,
Krithika

Krithika
shiva shankar
Ranch Hand

Joined: Jun 10, 2001
Posts: 84
Hi krithika,
As you said its working for me. Did you install websphere properly. Make sure you are in the local administrator's login. It is advisable for a novice to install WAS with Instant DB as the database
shiva
Krithika Venugopal
Greenhorn

Joined: Jun 14, 2001
Posts: 15
Hi,
I again installed Websphere logging in as administrator into my machine (and not my companies domain). Still the search does not give me any results. Should I give anything else in the Realm in Global setting other than Default? Should I enable any rights in the user rights in User Manager of NT Administrative tools?
Thanks,
------------------
Krithika
barry white
Greenhorn

Joined: Nov 09, 2001
Posts: 10
Hello Krithika,
i encountered the same problem with the local OS.
Did you find the solution?
If so could you tell me what to do urgently?
Thank you
Krithika Venugopal
Greenhorn

Joined: Jun 14, 2001
Posts: 15
Hello Barry,
If the Windows NT machine is a standalone node(not part of a windows NT domain), then the user registry refers to the local machine.
If the Windows NT server is a part of a Windows NT domain, then the user registry is a union of the domain controller�s user registry and the local machine�s user registry.
So if the Server is a part of the domain and the domain has many users, the service will hang. Even the IBM support people told me that this could be the reason. So you unplug the machine from the domain and log on to the server itself(and not onto the domain) and try configuring the security.
If you have any more problems, do reply.
barry white
Greenhorn

Joined: Nov 09, 2001
Posts: 10
Hi Krithika
Thank you for your answer.
But i have several questions.:
How do you know if the server is a standalone node?
How do you unplug the machine from domain?
What did you put on the realm?
thank you very much for your informations?
barry white
Greenhorn

Joined: Nov 09, 2001
Posts: 10
I forgot to ask you:
How do you know the security server ID?
How do you know the security server password?
thanks
Lorenzo Dee
Greenhorn

Joined: Nov 06, 2001
Posts: 3
This might be related. I found this in WAS Hints and Tips.
Search results box empty in "Grant Permissions" dialog of "Assign Security Permissions" wizard.
*** Abstract ***
'Search Results' box remains empty when searching for everyone ('*') in 'Grant Permissions' dialog of 'Assign Permissions' wizard of WebSphere 3.5.

*** Content ***
'Search Results' box remains empty when searching for everyone ('*') in 'Grant Permissions' dialog of 'Assign Permissions' wizard of WebSphere 3.5.
One scenario under which this happens is when the WebSphere server machine is a node of an NT domain, and 'local os' is specified as the authentication mechanism. The local id under which WebSphere is installed does not have access to the domain user ids.
A way to test whether this is the problem is by changing the Startup... properties of the WebSphere admin service to be an admin id of the domain, and then restarting WebSphere and retrying the Configure Resource Security task. This is not a workaround, however; it will cause WebSphere to fail. It is only a test for problem determination.
APAR PQ41781 has been submitted to correct the problem.
http://www-1.ibm.com/servlet/support/manager?rs=180&rt=0&org=SW&doc=1003417
barry white
Greenhorn

Joined: Nov 09, 2001
Posts: 10
Hello!
Does someone know what do they mean by changing the Startup... properties of the WebSphere admin service?Which file is it?
Thanks
barry
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: WAS 3.5.3 Local OS Security