| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| REFRESH SECURITY |
« View previous topic :: View next topic » |
| Author |
Message
|
| Kunal |
 Posted: Sat Mar 30, 2002 3:39 am Post subject: |
 |
|
Newbie
Joined: 25 Mar 2002
Posts: 5
Location: India
|
Hi ,
Will someone please explain in short what 'Refresh Security' means or
in what context is it used ? I was looking for this topic in the Sys.
Admin manuals (Security Chapter) but did not find a reference it !!.Preparing for the exams so need this info urgently.
Regards
Kunal
kunalaher@email.com
|
|
| Back to top |
|
 |
| chenulu |
| Posted: Sat Mar 30, 2002 10:20 am Post subject: |
|
|
Voyager
Joined: 27 Mar 2002
Posts: 87
Location: Research Triangle Park, NC
|
|
| Back to top |
|
|
| chenulu |
| Posted: Sat Mar 30, 2002 10:23 am Post subject: |
|
|
Voyager
Joined: 27 Mar 2002
Posts: 87
Location: Research Triangle Park, NC
|
Kunal,
Refresh security is a new functionality in V5.2..
Its a "runmqsc" command and the command is "REFRESH SECURITY(*)"
This command refreshes the cache with any changes to security.
In earlier releases, one had to restart the queue manager to pick up any
security changes (since the security authorizations were stored on disk), which with this new functionality, this restart can be
avoided.
The above command will dynamically update reflect the security changes ie.
changes issued through command "setmqaut"..
Hope this helps.
Chenulu |
|
| Back to top |
|
|
| Kunal |
| Posted: Sat Mar 30, 2002 5:47 pm Post subject: |
|
|
Newbie
Joined: 25 Mar 2002
Posts: 5
Location: India
|
Hi Chenulu,
Thanks for the quick response. I shall be looking in the manuals for more details .
Regards
Kunal
|
|
| Back to top |
|
|
| kolban |
| Posted: Sat Mar 30, 2002 8:20 pm Post subject: |
|
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
Changes made by setmqaut should be visible with or without refreshing security. What this command means is that the queue manager refreshes its security cachce of known relationships between users and groups by re-requesting such information from the operating system.
For example, if you add a new unix userid or group memebership while the queue manager is running, the queue manager will not see these changes until/unless the queue manager is restarted (old story) or until the refresh queue manager command is submitted (new story). |
|
| Back to top |
|
|
| cvshiva |
| Posted: Thu Apr 11, 2002 11:15 pm Post subject: |
|
|
Apprentice
Joined: 04 Mar 2002
Posts: 35
Location: Chennai
|
Hi Kolban,
That was a good point.
Kunal & Chenulu,
I also had the same doubt and thought that the Queue Manager has to be restarted after the setmqaut command , But it is not necessary to do so. The setmqaut will be reflected immediately during the next time when the user connects to the Queue Manager. If the User already has an open connection during the Setmqaut command, the changes will not be reflected to this open connection and User will be able to do everything that was allowed earlier to issuing the setmqaut command all thru the life of this open connection.
Hence it is always a good idea to stop applications with Open Connection to the Queue Manager and apply security and restart applications. This is the right way if you are doing it with the knowledge of the Application users, if not u can very well Restart the Queue Manager as a whole
_________________
Ramnath Shiva
IBM Certified SOA Specialist
IBM Certified MQSeries Specialist
Standard Scope International Pvt Ltd , Chennai |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
