Thanks Ayumu.     Hence the only authentication method for Tacker server should be using OAUTH2 token.  Is this right?

Regards,

Ravichandran

From: Ayumu Ueha (Fujitsu) <ueha.ayumu@fujitsu.com>
Date: Tuesday, 19 March 2024 at 3:10 PM
To: Ravichandran Venkataraman (veravich) <veravich@cisco.com>, openstack-discuss@lists.openstack.org <openstack-discuss@lists.openstack.org>
Subject: RE: Tacker REST API Authentication

Hi Ravichandran,

Thanks for your question,

> Is it possible to use username/password for authentication of Tacker REST API calls?

No, it is not able to use username/password for authentication of Tacker REST API calls.

You may have seen the following configurations,

https://docs.openstack.org/tacker/latest/configuration/config.html#authentication.auth_type

https://docs.openstack.org/tacker/latest/configuration/config.html#authentication.user_name

https://docs.openstack.org/tacker/latest/configuration/config.html#authentication.password

but the configuration above is not the configuration that Tacker as server.

This is the authentication configuration that Tacker uses for the external connection as the client as described in the description.

Regards,

Ayumu

From: Ravichandran Venkataraman (veravich) <veravich@cisco.com>
Sent: Saturday, March 16, 2024 12:11 AM
To: openstack-discuss@lists.openstack.org
Subject: Tacker REST API Authentication

Hi,

Is it possible to use username/password for authentication of Tacker REST API calls?

In the tacker.conf, I see both BASIC and OAUTH2 methods for authentication.  If I set the auth_type to BASIC and configure the user_name and password values, will I be able to make the REST calls with these username and password?

Thanks and regards,

Ravichandran