Hello Narushima-san, This is not something I have implemented myself, so forgive me if my comments are in any way misguided.
Per my understanding though, Ranger is all about *authorization*, not authentication. Ranger and Atlas should use the same *authentication* source - e.g. LDAP. That would be involved in getting users logged in in the first place. Then, *after* a user has confirmed their identity and logged in, *then* Ranger gets involved by *authorizing* what that user is allowed to see and do inside Atlas. In the Cloudera stack, we often use Apache Knox <https://knox.apache.org/> as the component to mediate between various authentication sources on the one hand (Active Directory, Okta, FreeIPA etc.) and the various big data tools on the other (Ranger, Atlas and so on). I hope this is somehow helpful. Kind regards, --Ryan On Mon, Apr 14, 2025 at 10:32 AM Masato Narushima <masato.narush...@riken.jp> wrote: > Hello, > I want to use Apache Ranger to manage Apache Atlas users. > If it is not correct to post here, please point it out. > > When I try to log in to Apache Atlas, I get the following message > Error while authenticating > Login process XXX returns 401. > No other information on logs is available. > > The following settings are used to confirm this. > > Specified in the Apache Atlas configuration file > (atlas-application.properties) > > atlas.authorizer.impl=org.apache.ranger.authorization.atlas.authorizer.RangerAtlasAuthorizer > atlas.authentication.method.kerberos=false > atlas.authentication.method.file=false > > Specify ranger-2.6.0-atlas-plugin > install.properties > Execute enable-atlas-plugin.sh > > The “test_ranger_atlas” service is configured for ranger and a user is > added. > > Apache Atlas Authentication not configured? > Please let us know if any necessary settings are missing or incorrect. > > Thanks & Regards, > Narushima > > >
