-
Notifications
You must be signed in to change notification settings - Fork 467
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Include IP address in the User Activity Log for Add, Modify, Delete user #30678
Labels
Comments
erickgonzalez
moved this from New
to Current Sprint Backlog
in dotCMS - Product Planning
Nov 18, 2024
gortiz-dotcms
moved this from Current Sprint Backlog
to In Progress
in dotCMS - Product Planning
Dec 3, 2024
gortiz-dotcms
added a commit
that referenced
this issue
Dec 4, 2024
gortiz-dotcms
added a commit
that referenced
this issue
Dec 4, 2024
Let's add the IP also when starting to exec the action |
gortiz-dotcms
added a commit
that referenced
this issue
Dec 5, 2024
github-project-automation
bot
moved this from In Review
to Internal QA
in dotCMS - Product Planning
Dec 11, 2024
Working as it should. Adding User:
Update User:
Delete User:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Parent Issue
No response
User Story
dotCMS logs do not currently include the user IP address in the User Activity logs for Adding a User, Modifying, and Deleting a User. DB is requesting that the IP address information be added to these logs as this is a requirement from their internal access control team.
Acceptance Criteria
The user IP address should be present in the user activity logs for Add, Modify, and Delete user.
Proposed Objective
Security & Privacy
Proposed Priority
Priority 2 - Important
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
https://dotcms.airfocus.com/DF-49
https://helpdesk.dotcms.com/a/tickets/28384
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered: