POST HTTP Action - Dayforce API - error invalid_client

[AnalogIT]

Hi, 

I'm wondering if someone can help me out as I've never experienced this before. I'm working with the Ceridian Dayforce API and am using a custom connector. I am trying to retrieve the bearer token and am receiving an {"error":"invalid_client"} on the HTTP action. When I follow the API requirements with postman I'm able to retrieve the token. When I use the HTTP action I get this error. 

Dayforce API Token-Based Auth documentation

Request a token

An authentication token can be retrieved with an API call to Dayforce Identity servers.

The call is a POST call on the following URLs:

• Production: https://dfid.dayforcehcm.com/connect/token
• Touch: https://dfid.dayforcehcm.com/connect/token
• Config: https://dfidconfig.np.dayforcehcm.com/connect/token
• Test: https://dfidtst.np.dayforcehcm.com/connect/token

You will need to join the following form body to your call:

• Grant_type: value is always: password
• CompanyId: Client namespace, used to connect to Dayforce UI or APIs
• Username: Name of the Dayforce user dedicated to Web service calls
• Password: Password of the specified user
• Client_Id: Scope of the token, the value is always: Dayforce.HCMAnywhere.Client

The content type of this body should be application/x-www-form-urlencoded.
 

Dayforce Identity server will check the credentials provided in the request and respond with JSON Web Token containing the token, its scope and its validity duration (in seconds).

[abm · Accepted solution]

Hi @AnalogIT 

Tried now and I got this working

By looking the documentation you don't need to pass the body in JSON format. Copy the below in your body and replace the relevant values.

grant_type=xxxxx&companyId=xxxx&username=xxxxx&password=xxxxx&client_id=Dayforce.HCMAnywhere.Client

See below my unit test result:

[AnalogIT]

Thank you very much @abm . That did the trick!

Do you know if it is possible, now that I have the bearer token to use that in a custom connector to authenticate? I realized after I went down this path that the custom connector uses built in authentication. (API, basic etc). 

I'm going to try no authentication on the custom connector and use header options to be able to place the bearer token in the header when the connecter is used in the flow. I have been using the username and password but I'd like to implement the renewable token as it would be more secure. 

Any insight would be much appreciated. 

[AnalogIT]

@abm - It looks like using the Authentication header information is not allowed in a custom connector. 

custom API connection using JWT that expires - Power Platform Community (microsoft.com)

[Anonymous]

Did you actually create a custom connector or are you just using raw http calls to Dayforce?

I ask because I am trying to create a custom connector myself for Dayforce but cannot see how to specify the authentication in the connector

I don't see how you can create a grant_type=password at all

[deepakt]

Hi,

I have queries as per below,

grant_type=xxxxx&companyId=xxxx&username=xxxxx&password=xxxxx&client_id=Dayforce.HCMAnywhere.Client

from the above url,

What is company id ? is this company name like xyz.com?

what is Username value ?  is this  email id like xyz@abc.com?

what is the Password value ? is this login password for that user?

Please suggest.

Thanks