Outlook plugin: app key

[sensei01]

For the outlook api we need to create a Microsoft Azure app. I create the app and I get some info such as client id, object id, etc (pic 1). The outlook plugin requires an “App key” (pic 2) value that I do not find in this screen. So, I also create a certificate hoping to see the app key but no such thing as app key (pic 3). Also, client secrets seem not to be related to the app key (pic 4). So, how/where am I supposed to get this app key?

Thanks.

[AntonZ]

Hello @sensei01 ,
Thank you for contacting us.

Typically, the “App key” in the context of Azure applications is synonymous with the “Client secret” or “Application secret.” This is a value that you generate in the Azure portal for your application, which is used to authenticate your application similarly to how a password is used with a username.

Here’s how you can generate a Client Secret (which should serve as the “App key”):

1. Go to your application in the Azure Portal.
2. Navigate to “Certificates & secrets” under the “Manage” section.
3. Under the “Client secrets” section, click on “New client secret.”
4. Add a description for your secret and choose an expiration period.
5. After clicking “Add,” the value of the client secret will be displayed. You must copy this value immediately as it won’t be shown again for security reasons.

This client secret is what you would enter into the “App key” field in your Zeroqode Outlook plugin configuration.

Please make sure you handle this key securely as it allows access to your Azure application and, by extension, any resources it’s authorized to access.

Also, I have checked our documentaion and demo editor page of this plugin and concluded that everything is working as it should. Below I have attached a screenshot from our demo editor page showing how our workflow is configured using the Api key you mentioned earlier

If after what I have pointed out above, you are not able to solve the problem, please send a screenshot of the error.

Cheers!

[sensei01]

hey @AntonZ
This is what I do:

1. create the app
   

   

2. create client secret
   

   

3. add client secret to bubble app
   

   

This is the error I get:

Thanks

[sensei01]

@AntonZ I also tried to select “Personal microsoft account only” in the first page but with no effect. Here is where you can create apps: Microsoft Azure and try yourself. In the “app key” in bubble I enter the client secret value even if the picture in bubble does not reflect that.

[sensei01]

@AntonZ
I think I found the issue. There are two things to keep in mind:

1. when creating the app select the option “accounts in any directory and personal acounts”
2. in the “app key” you should enter the “application (client) id”

[AntonZ]

Hello @sensei01,
Thank you for your quick response.

I’m very glad you were able to find a solution to this problem, and thank you for sharing this information with us!

Please let me know if there is anything else I can help you with.
Cheers!

[sensei01]

@AntonZ What am I doing wrong here?
I get “access denied” when trying to create an event. video

[sensei01]

@AntonZ any input on this would be appreciated. Thanks.

[AntonZ]

Hello @sensei01 ,
Thank you for your reply and sorry for the long waiting due to the weekend.

I have passed this information to the development team, they will check it and we will get back to you as soon as possible.

Thank you for understanding.
Cheers!

[sensei01]

@AntonZ Any update on this one? Thanks.

[AntonZ]

Hello @sensei01 ,
Thank you for your patiecne.

After a careful review of the situation, it appears that the issue you’re encountering with token expiration is linked to the ‘expires on’ state not being utilized on your page. This oversight likely causes the token to expire, leading to access issues.

To address this, I recommend that you incorporate the ‘expires on’ state into your page setup. This change should help maintain the token’s validity and ensure uninterrupted access after authorization.

I’ve attached a screenshot that should guide you through this process. Please take a moment to review it and recreate the setup as shown.

Also, please check our plugin page and try to recreate our setup.

If you have any additional questions, please feel free to ask.

Cheers!

[sensei01]

Thanks, @AntonZ I think I managed to make it work.
Just one last question. I see that expires on is the time in UNIX milliseconds. So, it basically is the current time.
What is its purpose? I though that the purpose of expire_on was that the access token expired on that date and we would have to refresh the access token.

Thanks.

[AntonZ]

Hello,
Thank you for your patience and sorry for long reply.

I wanted to address your recent query regarding the ‘expires_on’ attribute in the context of access tokens.

The ‘expires_on’ field contains the timestamp marking when the token will expire. This expiration is set to one hour from the moment the token is created. Once this time elapses, the program will automatically refresh the token.

It’s important to note that the ‘expires_on’ time is not the current time but rather the creation time of the token plus one hour. This mechanism is designed to prevent the need for users to repeatedly log in with each page refresh.

I hope this explanation clarifies your doubts. If you have any further questions or need additional assistance, please feel free to reach out.

Cheers!