Hi Packetfence users, According to the following guide from 2018, it seems that 2FA isn’t considered during authentication. Now the SentinelOne portal requires an api token or password with 2fa token.
https://packages.inverse.ca/PacketFence/doc/PacketFence_SentinelOne_Quick_Install_Guide.pdf Could anyone please advise? Or is there a newer guide? Thank you. Kind regards, Albert On Wed, 1 Jun 2022 at 4:36 PM, Albert Yung <[email protected]> wrote: > > We are testing out a configuration where users have to install a security > agent SentinelOne, in order to gain access to a server. > > While we try to integrate PF 11.2.0 with SentinelOne API by following the > integration guide, we got an error 401 in packetfence.log. > > pfperl-api (101408) ERROR: failed to get token from SentinelOne API : 401 > UNAUTHORIZED (pf::provisioner::sentinelone::fetch_token ) > pfperl-api (101408) ERROR: Cannot authenticate against SentinelOne API. > Please check your configuration. > (pf::provisioner::sentinelone::execute_request ) > > In the provisioner configuration, we filled in the fields as follows: > > Host: apne1-xxx.sentinelone.net > > Port: 443 > > Protocol: https > > API username: sample > > API password: xxxxxxxxxxxxxx > > > I have created an API token from SentinelOne admin portal with > "Authorization: ApiToken” as a header and used it successfully from another > API client. > > May I know in the field API password, is it correct to put in the > generated API token? This is because if I put in the user password, an MFA > token will be required to login and therefore it will be unsuccessful. Any > suggestions? > > Thanks so much. > > Best regards, > Albert Yung > *Quadtron Ltd* > > > -- Regards, *Albert Yung* *Quadtron Limited* M: +852 8191 2594 Email: [email protected] Unit 1102, 11/F, 88 Gloucester Road Wan Chai, Hong Kong
_______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
