AnsweredAssumed Answered

Authentication for service Accounts in Aveksa

Question asked by shakti nayak on Jan 29, 2018
Latest reply on Feb 22, 2018 by Sunita Bhat

Like • Show 0 Likes0
Comment • 6

I want to create a local account in Aveksa, similar to AveksaAdmin but with least privileges and to use default Aveksa Authentication, mainly to by pass SSO.

I have followed the steps in the below link

Authentication Sources - Web Services

How to create local-account in aveksa (other than AveksaAdmin) to bypass SSO

Created a trusted source system using a csv to store service account and password.
Added the aveksa priveleges to call the webservices
But the next step tells to add the trusted source system as an authentication source but i can only see 3 types of authentiction sources present LDAP/AD or SSO. or TestProvider

How do i "Add the trusted source system as an authentication source".

No one else has this question

Outcomes

shakti nayak Jan 31, 2018 10:44 AM

Any suggestions ?

Actions

Pradeep Kadambar

@ shakti nayak on Jan 31, 2018 10:50 AM

LDAP is the only source (for direct bind) supported.

You should create the service account in AD in specific OU and collect them as identities. You can configure an AD auth source.

Actions

shakti nayak @ Pradeep Kadambar on Jan 31, 2018 10:59 AM

I was referring to the below discussion:-

How to create local-account in aveksa (other than AveksaAdmin) to bypass SSO

My requirement is to have some local accounts who can authenticate in Aveksa like Aveksa Admin

I would like some clarity on the below.

"Create the service account in a trusted source system. This could a directory, a database or even a CSV file if you adequately secure the file. Add the service account with a secure password to the trusted source. Collect the service account into Aveksa as an identity. Add the relevant Aveksa privileges to the user to be able to call the web services that are required. Add the trusted source system as an authentication source. When you login using the web service authenticate with the credentials in your source system. You only need to do this for web services that require authentication, some REST web services do not require an authentication token."

Actions

Sunita Bhat @ shakti nayak on Feb 12, 2018 2:05 PM

Use the TestProvider.

Your new user is coming from the CSV file.

Password would be what you give on the UI after selecting the TestProvider.

Actions

shakti nayak @ Sunita Bhat on Feb 14, 2018 9:20 AM

Thanks for the update.

But the TEST Provider leads to a default password for every account.

Which we don't want.

So looking for any alternative options.

Actions

Sunita Bhat @ shakti nayak on Feb 22, 2018 11:47 AM

That's true. In my use-case we wanted just two additional accounts so we created two such IDCs and gave different password for each.

I will be interested too in any alternate solution.

Actions

6 Replies

shakti nayak Jan 31, 2018 10:44 AM
Mark Correct
Correct Answer
Any suggestions ?
Like • Show 0 Likes0
Actions
- Pradeep Kadambar @ shakti nayak on Jan 31, 2018 10:50 AM
  Mark Correct
  Correct Answer
  LDAP is the only source (for direct bind) supported.
  
  You should create the service account in AD in specific OU and collect them as identities. You can configure an AD auth source.
  Like • Show 2 Likes2
  Actions
  - shakti nayak @ Pradeep Kadambar on Jan 31, 2018 10:59 AM
    Mark Correct
    Correct Answer
    I was referring to the below discussion:-
    How to create local-account in aveksa (other than AveksaAdmin) to bypass SSO
    My requirement is to have some local accounts who can authenticate in Aveksa like Aveksa Admin
    I would like some clarity on the below.
    
    "Create the service account in a trusted source system. This could a directory, a database or even a CSV file if you adequately secure the file. Add the service account with a secure password to the trusted source. Collect the service account into Aveksa as an identity. Add the relevant Aveksa privileges to the user to be able to call the web services that are required. Add the trusted source system as an authentication source. When you login using the web service authenticate with the credentials in your source system. You only need to do this for web services that require authentication, some REST web services do not require an authentication token."
    Like • Show 0 Likes0
    Actions
    - Sunita Bhat @ shakti nayak on Feb 12, 2018 2:05 PM
      Mark Correct
      Correct Answer
      Use the TestProvider.
      Your new user is coming from the CSV file.
      Password would be what you give on the UI after selecting the TestProvider.
      Like • Show 0 Likes0
      Actions
      - shakti nayak @ Sunita Bhat on Feb 14, 2018 9:20 AM
        Mark Correct
        Correct Answer
        Thanks for the update.
        But the TEST Provider leads to a default password for every account.
        Which we don't want.
        So looking for any alternative options.
        Like • Show 0 Likes0
        Actions
        Sunita Bhat @ shakti nayak on Feb 22, 2018 11:47 AM
        Mark Correct
        Correct Answer
        That's true. In my use-case we wanted just two additional accounts so we created two such IDCs and gave different password for each.
        I will be interested too in any alternate solution.
        Like • Show 0 Likes0
        Actions

Authentication for service Accounts in Aveksa

Outcomes

Related Content

Recommended Content