Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Document LDAP/access errors and the corresponding tag to fix

Description

When a user tries to access a feature and is denied access - this shows an error message.

Possibly add either:

1) Add to that error message the access tag (as seen in ConfigMgr) the user needs access to

or...

2) Provide a table mapping the two - e.g.,
"<error message>..."   -->   "OthersWorkunitsAccess"

(This is more obvious in some cases than others.)

Conclusion

None

Activity

Show:

Russ Whitehead September 27, 2023 at 2:17 PM

This would be done in ESP

Russ Whitehead May 22, 2023 at 8:53 PM

How would we go about adding the resource name to all permission error messages?  Is this in the generated code, based on the resource name specified in the ECM ?

Kanghua Wang May 8, 2023 at 5:43 PM

I think we should.

Russ Whitehead May 8, 2023 at 5:37 PM

Do you guys think it would be good to add the resource name (CodeSignAccess, FileIOAccess, etc) to the error message when user's are denied? 

Russ Whitehead March 6, 2023 at 8:45 PM

any reason we shouldn't include the LDAP Resource name in a permission denied message (CodeSignAccess, FileIOAccess, FileScopeAccess, etc) ? 

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Components

Assignee

Reporter

Priority

Compatibility

Minor

Fix versions

Pull Request URL

Roadmap

Not applicable

Created October 30, 2019 at 8:28 PM
Updated February 2, 2024 at 12:25 PM
Resolved February 2, 2024 at 12:25 PM