ramackri opened a new pull request, #1105: URL: https://github.com/apache/ranger/pull/1105
## Summary https://issues.apache.org/jira/browse/RANGER-5703 - Remove the remote Unix authentication stack: `unixauthservice`, `unixauthclient`, `unixauthnative`, and `unixauthpam` (TCP listener on port 5151, `RemoteUnixLoginModule`, and native validators). - Add `UserSyncService` as the usersync JVM entry point (HA latch, `UserGroupSync`, optional metrics) and relocate usersync install scripts/config from `unixauthservice/` into `ugsync/`. - Move local Admin PAM JAAS classes (`PamLoginModule`, etc.) into `security-admin`; `authentication_method=UNIX` and `PAM` both use local PAM on the Admin host via `ranger.pam.service`. - Update distro assemblies, install/setup scripts, threat model, and add `docs/UNIXAUTHSERVICE-REMOVAL.md` with migration notes. **Not removed:** UserGroupSync (LDAP/file/Unix sources), Admin local PAM (`PamLoginModule` / libpam4j), LDAP/Kerberos/JDBC auth. ## Test plan - [ ] `mvn test -pl ugsync -Dtest=org.apache.ranger.usergroupsync.TestUserSyncService` - [ ] `mvn test -pl security-admin -Dtest=org.apache.ranger.security.handler.TestRangerAuthenticationProvider,org.apache.ranger.authentication.unix.jaas.TestPamLoginModule` - [ ] Build usersync and admin tarballs (`mvn package -Pranger-usersync`, admin assembly) - [ ] Verify usersync starts with `UserSyncService` main class (not `UnixAuthenticationService`) - [ ] On-prem: confirm Admin PAM login still works with `ranger.pam.service` configured - [ ] Confirm deployments using remote Unix auth (`RemoteUnixLoginModule` / port 5151) migrate to local PAM or LDAP before upgrade Made with [Cursor](https://cursor.com) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
