Hi Koen,

It looks like the process of retrieving the JWT and setting it as a cookie worked fine as the get configuration URL used is in the correct format and the request did not return a 401000 error. The JWT that is being passed in the Authorization header is deemed to be invalid by the Authorization Service on the backend.

Were you able to successfully login on the webclient used to retrieve the token?

Thanks,
CIS Support Team

Hi Koen,

The authenticationInfo.tokens property accepts an array of strings which act as a whitelist. By setting

authenticationInfo: { enabled: true, tokens: ['Authorization'] }

you are instructing the token provider to search through a collection of tokens and apply it to the header when making a request. This token must be added to the token collection using

clientSession.setToken({header: 'Authorization', value: token});

before a request requiring the header to be set can be made.

For example...

  const authToken = {header: 'Authorization', value: token};



  // UAC Configuration for Avaya Customer Services SDK

  const config = {

    uacConfiguration: new AvayaCustomerServices.Config.UACConfiguration({

      ...

      authenticationInfo: {enabled: true, tokens: ['Authorization']}

      ...

    })

  };



  // Initialize the Avaya Customer Services SDK

  const client = new AvayaCustomerServices(config);



  // Start Client Session service

  const clientSession = client.createClientSession();



  // Set token to SDK token store

  clientSession.setToken(authToken);



  // Handle callback when configuration is loaded from UAC

  clientSession.getConfiguration(authHandle).then((configuration) => {......}

Regards,
CIS Support Team

Hi Koen,

Could you paste the response text that you get back the GET request?

Regards,
CIS Support Team

Hi,

1. correct,
2. also correct - currently Workspaces on Oceana, and Workspaces on Elite do not support multiple Agent Client Sessions - so you can't be logged in to Workspaces and another client at the same time. You should raise this requirement with Avaya Product Management to prioritise for future releases.
3. this I have no knowledge on - can you raise a ticket in the "Avaya Breeze" forum, and ask the question there.


Best regards

CIS Support Team

Hi,

The example shown is just a suggestion - you need to replace the 'UACCookieSession' cookie, with the name of the Authorization SSO cookie you have created.
UAC is only used for authenticating Workspaces Users, and is not suitable for authenticating Users from other Clients - you will need to integrate with the Breeze Authorization service to do this.

See here for information on this (for Oceana 3.6):
https://www.devconnectprogram.com/site/global/products_resources/avaya_breeze/releases/3_6/index.gsp#tabs-product-downld-2

In Downloads > Programming Resources > Authorization Helper APIs for External Clients, Avaya Breeze Platform Release 3.6

Best Regards

CIS Support Team

Hi Michael,

Do you have access to an Administrator login to a Workspaces installation?
The Workspaces Widget documentation (and samples) are shown to you when you login to Workspaces as an Administrator.

Best Regards,

CIS SDK Package Support

Yes, that is correct. Manual In / Auto In is for Elite only

Hi Chris,

Are you using the Breeze CSDK with an Elite environment? The "MANUAL_IN" / "AUTO_IN" feature works on Elite only and has no effect when it is used with Oceana.

Regards,
John

Hi Chris,

This is a function of how Oceana works - there is no ability to have multiple Agent logins, and as such the second session logs out the first.

Agent's shouldn't be sharing accounts, this is bad practice.
At the very least, Agent accounts shouldn't share the same password - this is very bad practice.

Maybe displaying an intermediate page to the Agent where they verify their details before proceeding with the Activation step is the way to go - this is what Workspaces does.

Best Regards

CIS Support Team

Hi,

What version of the SDK are you using?

1.This callback is fired when the state of the Interaction is 'ACTIVE', and will trigger for each event received from the back-end in that state.
2. Which Event is fired after the activate method is called? do you mean the agent onActivatedCallback?
3. This would trigger if the state of the Interaction was 'UNHELD', probably what is happening is that the state Interaction is going to 'ACTIVE' after unholding, so the above event will trigger.
4. I do not follow this - are you saying that Agents are sharing the same PC session?, or is this just happening on the developer PC?

Best Regards

CIS Support Team

Hi,

Again, you really need to be checking the capabilities - if you checked the Interaction 'canConferenceComplete' capability you would have seen that it was false.

rgds

CIS Package Support

Hi,

If you are seeing the same issue in Workspaces then this is not an SDK activation issue - please escalate through Avaya Oceana support as necessary.

thanks

CIS Package Support

Hi,

This looks like a configuration issue - what error are you getting back when you do the same in Workspaces?

To see if an error is being raised (instead of poking around in the low-level parsers) you can attach a callback as such:

clientSession.addOnErrorCallback(function (data) {

            console.log(data);

        });

thanks

CIS Package Support

Hi,

There are many reasons why this mightn't happen.

The URL you pasted was for the agent login request, not agent activate request.

What does the console log show for agent.isActivated()?, what are the agent capabilities at this point? specifically is 'canLogin' true?

The promise that you are firing after the active.activate() call will fire when the activate request has completed - the agent will not be activated at this point. You need to add a callback on the agent object to be notified when the agent has been activated.

see:

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

agent.addOnActivatedCallback(function (agent) {

  console.log('Agent Client Session has been successfully activated');

});

rgds

CIS Package Support

Hi,

looks like the username isn't being passed.

your URL should be : http(s)://{ip}/UAC/UACAPI/users/{username}/sessions/....


thanks

CIS Package Support