Error testing authentication scheme on Google calendar

[ciche...@fater.it]

Hello,
I am testing the authentication scheme "Login/Password" with "Retrieving all calendars".

I changed the test environment scheme of the provider and I put the user@domain+password as required.

Now, running the connector, it gives "Unknown authorization header".
Is it possible to have more info on the error and the cause ?

Thank you,
Luigi

[Gareth Thiveux]

Hi Luigi,

You should have kept the custom authentication scheme of your Google Calendar provider.

Url live/test : https://www.google.com/calendar/

Authentication scheme : Custom

Scheme name : GoogleLogin

Credentials : auth=${Auth}

As you see, an Auth variable is required in order to be authenticated. This Auth value will be generated thanks to another connector "Login Calendar" connector that you can find under the "Google API Login" provider in the library (note that it's a different provider from the one mentionned before, so when importing the connector you shouldn't attach it to "Google Calender" provider you already have, but choose the "Import connector provider as defined in the library" option, unless you have already imported that provider before for any other purposes (Login to a Google Document or Spreadsheet for instance).

You'll then have at least two boxes in your process following each other, the first one with the "Login Calendar" connector plugged on it (and this is where you'll have to define login and password as inputs), and the second one with the "Retrieve all calendars" connector on it.

Hope it's clear enough.

Don't hesitate to come back to us if you need further details or other explanations.

Regards,

Gareth THIVEUX   

Consultant Avant-Vente / Pre-Sales Consultant

 Fujitsu RunMyProcess

22 rue Chauchat, 75009 Paris - France (GMT+1)

website : Fujitsu RunMyProcess      

Fujitsu RunMyProcess user? Please add a review on GoogleApps Marketplace

Afin de contribuer au respect de l'environnement, merci de n'imprimer ce message qu'en cas de nécessité.
Be environmentally friendly: do not print this email unless it is entirely necessary.

2013/7/15 <ciche...@fater.it>

--
Fujitsu - RunMyProcess
---
You received this message because you are subscribed to the Google Groups "RunMyProcess Support Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to supportforum...@runmyprocess.com.
To post to this group, send email to suppor...@runmyprocess.com.
Visit this group at http://groups.google.com/a/runmyprocess.com/group/supportforum/.
For more options, visit https://groups.google.com/a/runmyprocess.com/groups/opt_out.

[ciche...@fater.it]

Thank you, Gareth, your reply was very clear.

I tested and it works but, in this way, I need to have the user+password CLEARLY EXPOSED into the input variables of login box.
That's why I first thought to use the authentication scheme="Login/Password".

Is there any way to secure id/password ?
When should I used the login/password scheme ?

Best Regards,
Luigi

[Gareth Thiveux]

Hi Luigi,

Well in next to your input variables of the login box you can tick the "secured" checkbox, so that they won't be visible in the parameters of your process instances.

You can also directly type login and password in the Login Calendar connector itself, by replacing ${login} by the login and ${password} by the password in the Content of the connector.

I haven't got examples in mind right away about when to use the login/password scheme, but it is used when any Basic authentication is required.

Regards,

Gareth THIVEUX   

Consultant Avant-Vente / Pre-Sales Consultant

 Fujitsu RunMyProcess

22 rue Chauchat, 75009 Paris - France (GMT+1)

website : Fujitsu RunMyProcess      

Fujitsu RunMyProcess user? Please add a review on GoogleApps Marketplace

Afin de contribuer au respect de l'environnement, merci de n'imprimer ce message qu'en cas de nécessité.
Be environmentally friendly: do not print this email unless it is entirely necessary.

2013/7/17 <ciche...@fater.it>

Luigi

[ciche...@fater.it]

On Monday, July 15, 2013 4:59:08 PM UTC+2, ciche...@fater.it wrote:

One more doubt, Gareth,about the "Auth":
I suppose that I can use the "auth" result after "Google API login" not only for
Google Calendar connectors but also for Google Sites connectors, Google Documents connectors, etc...
Is it true ?
Have the "auth" created with "Google API login" an expiration, that is,
if the process starts and create the "auth" and then a step will use it but even one month later, coult it be a problem ?

Thanks again,
Luigi

[Gareth Thiveux]

Hi Luigi,

Each Google resource has its own Login connector (Login Calendar, Login Documents, Login Spreadsheet, Login Google Site ...) that you can find under the Google API Login provider in the connectors library. It's the same provider as you've noticed, but not the same connectors (So if you decide to import any of these other Google resource Login connector, you won't need to import the provider again, you'll be able to attach to your already imported Google API Login provider).

Yes, the "Auth" created thanks to the Login connector has an expiration, which is probably 24h, like most of Google tokens.

So if you any Google connector that needs this Auth to be generated before, you'd better add the Login connector box just before the box that needs the Auth.

Regards,

Gareth THIVEUX   

Consultant Avant-Vente / Pre-Sales Consultant

 Fujitsu RunMyProcess

22 rue Chauchat, 75009 Paris - France (GMT+1)

website : Fujitsu RunMyProcess      

Fujitsu RunMyProcess user? Please add a review on GoogleApps Marketplace

Afin de contribuer au respect de l'environnement, merci de n'imprimer ce message qu'en cas de nécessité.
Be environmentally friendly: do not print this email unless it is entirely necessary.

2013/7/17 <ciche...@fater.it>

On Monday, July 15, 2013 4:59:08 PM UTC+2, ciche...@fater.it wrote:

Luigi