[Stephen]

What is the function of the "trusted systems" located within the configuration?

[Wes Barnes]

Stephen, on 22 January 2010 - 06:04 AM, said:

What is the function of the "trusted systems" located within the configuration?

Trusted systems are users or accounts used by the EchoSystem server API for authentication. Each user or system that needs to interact with the API must have a Key and Shared Secret to authenticate and retrieve or submit information. The API follows the OAuth implementation used by many API systems on the market. I have included a link to the documentation below that should help with this information.

http://docs.echo360....%20Started.html
Wes

[Jo@ucl]

Wes Barnes, on 22 January 2010 - 03:38 PM, said:

Trusted systems are users or accounts used by the EchoSystem server API for authentication. Each user or system that needs to interact with the API must have a Key and Shared Secret to authenticate and retrieve or submit information. The API follows the OAuth implementation used by many API systems on the market. I have included a link to the documentation below that should help with this information.

http://docs.echo360....%20Started.html
Wes

I'm embarrassed about asking such a basic question but I want to start learning how to use the scheduling API and don't understand what I need to put in each of the fields:
System name, Description and Consumer key
System name of what?

[Wes Barnes]

Jo@ucl, on 04 June 2010 - 11:26 AM, said:

I'm embarrassed about asking such a basic question but I want to start learning how to use the scheduling API and don't understand what I need to put in each of the fields:
System name, Description and Consumer key
System name of what?

Hi Jo --

I am sorry for the delay in responding but wanted to get back to you. The system name and description fields are used to describe the integration being performed. These values really can be anything you want. Same with the consumer key although, this is used when executing transactions against the API. After the three fields are populated and you click save, a consumer secret is created. The consumer key and secret are used to authorize all transactions against the API.

I have created a quick tutorial on this if you want to review it, I used an example of integrating with Banner but it can really be anything that you like.

http://training.echo...52-cfd3d7ed9e1a

I hope that this helps.

Wes

[Jo@ucl]

Wes Barnes, on 07 June 2010 - 03:32 PM, said:

Hi Jo --

I am sorry for the delay in responding but wanted to get back to you. The system name and description fields are used to describe the integration being performed. These values really can be anything you want. Same with the consumer key although, this is used when executing transactions against the API. After the three fields are populated and you click save, a consumer secret is created. The consumer key and secret are used to authorize all transactions against the API.

I have created a quick tutorial on this if you want to review it, I used an example of integrating with Banner but it can really be anything that you like.

http://training.echo...52-cfd3d7ed9e1a

I hope that this helps.

Wes

Thanks Wes, that answers my question