Hi Lars,

the infrastructure requirements for each package are outlines here:

https://www.devconnectprogram.com/site/global/products_resources/avaya_client_sdk/programming_docs/current/introduction/

currently, the CIS package requires Oceana.

Best Regards,

IDMS Package Support

Hi,

you need to use the IDMS package to authenticate first, before activating the User using the CIS package.

See here for a complete example:

https://www.devconnectprogram.com/site/global/products_resources/avaya_client_sdk/programming_docs/current/javascript/customer_interaction/guide/tutorial_auth.gsp

The Auth User is the ldap account associated with an Oceana User.

rgds

IDMS Package Support

Hi Don,

Thanks for that.

Again, does the sample app from the 3.0.0.1 work for you when you update the 'apiUrl'?

I used you code snippet in the sample app, without problem - here is how I referenced the config:

var client = new AvayaIdentityServices(environment.config.AvayaIdentityServicesConfiguration);

Is this similar to how you're doing it in your app?
What other libraries are you using? Angular 2?

You say the last attempt was unsuccessful - can you give more details? what querystring was passed? what response was received?

thanks

IDMS Package Support

Hi Don,

Thanks for your patience.

The SDK version doesn't need to be set, it is sent by the 3.0.0.1 package transparently.
Does the sample app from the 3.0.0.1 work for you when you update the 'apiUrl'?

These are the required properties for the configuration object:

var config = {
	serverInfo: {
		apiUrl: 'https://{UAC}/services/UAC/UACAPI'
	},
	clientInfo: {
		id: 'testApp'
	},
	enabled: true
};

thanks

IDMS Package Support

Hi Don,

OK, I see the problem - the version of the SDK that works with UAC version 3.2.1 is the 3.0.0.1 release (UAC 3.2.0 works with the 3.0.0.0 SDK).
Can you download that, and try the sample app and let me know if it works for you.

http://www.devconnectprogram.com/site/global/products_resources/avaya_client_sdk/developer_downloads/3_0_0_1/index.gsp

thanks,

IDMS Package Support

Hi Don,

thanks for the reply.

Can you tell me what version of the SDK is being sent up in the querystring for the auth request - i.e. open the network tab in chrome dev tools, and you should be able to see the request.

thanks,

IDMS Package Support

Hi Don,

have you tried the example application bundled with the SDK package?, or the 'get started' code sample here:

http://www.devconnectprogram.com/site/global/products_resources/avaya_client_sdk/programming_docs/current/javascript/identity_management/guide/tutorial.gsp

You should be able to just change the 'apiUrl' in the sample app, and get it to work straightaway.
What exact HTTP Response Code are you seeing - 400?.
Are you seeing a response body being returned?, and if so what is it?
Also, make sure to use 'https' when specifying the 'apiUrl'.
Also, can you specify the version of UAC & the SDK that you are using.

thanks,

IDMS Package Support