PQ62684: CREATE ACCESSID AT RUNTIME IF THEY HAVE NOT BEEN CREATED. | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Customer is adding to Role Group Roles using WSCP, WSCP did not create and AccessID in the process. The results are authorization exceptions when using the group.Local fix Manually add Roles to Group Roles through the AAT tool but this is too manual a process due to the large volume of users and nodes etc.Problem summary **************************************************************** * USERS AFFECTED: All WebSphere Application Server users * * adding groups to Roles via WSCP. * **************************************************************** * PROBLEM DESCRIPTION: Authorization failures for members of * * groups that were added to a Role via * * WSCP. * **************************************************************** * RECOMMENDATION: * **************************************************************** Authorization failures for members of groups that were added to a Role via WSCP. The problem stemmed from the fact that WSCP was not inserting an access ID for the group, which is used internally by WebSphere for authorization, into the Role.Problem conclusion The security runtime now creates an access ID if it is missing.Temporary fix testing eFix was send to customer.Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
SRLS
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ62684
IBM Group: Software Group
Modified date: Jun 28, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.