Adobe Journey Optimizer

Ikmoo · 4/10/23

Hi,

I am trying to integrate the eloqua Oauth2.0 using custom action inside AJO. I got two approaches,

1. Use autorization_code method. Here I need to hit authorize endpoint to get the code which can be used in another endpoint to get the access token. This doesn't look feasible to use inside the custom action.

2. Use of password as grant type. This works well but the issue is the authorization can be made only once per 60 seconds which if I use inside the journey only one profile works remaining all goes to error path due to this configuration.

Anyway possible to overcome this issue.

Thanks in Advance.

Anuhya-Y · 4/10/23

@Ikmoo

You can use custom authentication to generate access token. I worked on custom action integration with SFMC, calling access token end point and then using the access token in the main end point.

Check out https://medium.com/@anuhyareddy.y/ajo-jo-sending-email-delivery-via-3rd-party-marketing-automation-t...

Ikmoo · 4/10/23

Hi Anu,

Thanks for the response. I have already tried the custom authentication method and configured it . I am able to hit the endpoint and get the access token but the problem is every time system try to hit the endpoint it throws error that it has reached the limit.

I am using following method,

POST https://login.eloqua.com/auth/oauth2/token
Authorization: Basic Q09NUEFOWVhcdXNlcjE6cGFzc3dvcmQxMjM=
{
   "grant_type":"password",
   "scope":"full",
   "username":"testsite\\testuser",
   "password":"user123"
}

Tried via postman and got this error

So if I use it inside journey only one profile is able to trigger while other profiles are getting into error path as it tries to auth everytime . Any idea on this ?

Anuhya-Y · 4/10/23

Looking at the error message, I believe it should be fixed from Eloqua end. Please reach out to Eloqua team.

_Manoj_Kumar_ · 4/10/23

Hello @Ikmoo

AJO, by default, does not throttle the API calls. But as an industry standard, the API requests are throttled to 60 requests per min.

You are facing the same issue. AJO is trying to make more than 60 requests to Eloqua within a min.

This can be fixed by asking Eloqua to increase the API Rate limit for your instance.

Manoj
Find me on LinkedIn

Ikmoo · 4/11/23

Hi @_Manoj_Kumar_

Thanks for the response. the problem is I am using this custom auth method and the very first time the test is successful but if I click the test again I am getting this error similar to what I am facing from the postman(attached SS in earlier post) . This is without even trying inside the journey.

For this also problem can be solved in eloqua end ? if so any idea how to configure there ?

Thanks in Advance!