User Profile
karamem0
Brass Contributor
Joined 7 years ago
User Widgets
Recent Discussions
Re: Supports API-Key or X-Functions-Key in API-based message extension
Prasad_Das-MSFT Thank you for replying, I will post the feedback. As a workaround, I can convert Beaer token to X-Functions-Key header using APIM. <set-header name="X-Functions-Key" exists-action="override"> <value>@(Regex.Match(context.Request.Headers.GetValueOrDefault("Authorization",""), "^Bearer (?<key>.+)$").Groups["key"]?.Value)</value> </set-header>Re: Supports API-Key or X-Functions-Key in API-based message extension
Prasad_Das-MSFT My idea is Teams detects OpenAPI Security Schema when specified authType: apiSecretServiceAuth. https://spec.openapis.org/oas/v3.0.1#security-scheme-object manifest.json "composeExtensions": [ { "composeExtensionType": "apiBased", "authorization": { "authType": "apiSecretServiceAuth", "apiSecretServiceAuthConfiguration": { "apiSecretRegistrationId": "9xxxxb0f-xxxx-40cc-xxxx-15xxxxxxxxx3" } } swagger.json "securitySchemes": { "apikeyheader_auth": { "type": "apiKey", "name": "X-Functions-Key", "in": "header" } }Supports API-Key or X-Functions-Key in API-based message extension
Hi all, I am tring to imprement a Teams app with API-based message extension. The backend of the API is Azure Funtions HTTP trigger and requires an API key. The API-based message extension supports the API key authentiation, but the key is sent as Bearer token (Authtorization header). Unfortunately, Azure Funtions does not supports Bearer token. Also I tried to include an OpenAPI security schemas, but it was ignored. Some other API (e.g. OpenAI Service) accepts an API key with API-Key header. I think it is not common method to send an API key with Bearer token. I think it is helpful that the users can specifiy the authencation method (by OpenAPI spec, maybe).Deep link to channel tab does not work in new Teams (v2)
I am getting the web URL of teams tab using Graph API. Request: GET https://graph.microsoft.com/v1.0/teams/07a93f.../channels/19:ba1a...@thread.tacv2/tabs/... Response: { "id": "...", "displayName": "Calendar", "webUrl": "https://teams.microsoft.com/l/channel/19%3a..." } In v1 (Teams classic) I could open a tab directly using webUrl. but I got an error in new Teams (v2). The error message: "Error: Unsupported tab type" Is it any idea to resolve the issue?GET /v1.0/teams/{id}/channels returns HTTP 403 error
I met HTTP 403 error when invoking GET /v1.0/teams/{id}/channels request. The error message is: { "message":"Request is not allowed for externally authenticated users", "errorCode":"GuestAccessDenied" } I have granted the Channel.ReadBasic.All permission to Azure AD app and the access token has Channel.ReadBasic.All scope. The delegated user is a guest user, but the same request was successfully invoked in past. There are no change in Teams Admin settings and Azure AD settings. I want to know how to resolve the issue. Is it caused by any settings?Mgmt.AppCatalog.LOBApp.Upload.BadRequest.UnknownTeamsAppManifestExceptionType error has occured
I cannot upload custom app into organization because Mgmt.AppCatalog.LOBApp.Upload.BadRequest.UnknownTeamsAppManifestExceptionType error has occured. What I tried: I tried to upload same app to other tenant but got same error. I tried to upload other app but got same error. What happened?Re: "Manifest parsing has failed." in Developer Portal
Sayali-MSFT I imported the manifest file and I clicked "Preview in Teams". The error is resolved but nothing happen. I think the install dialog will be shown after clicked "Preview in Teams". Also I found the difference. The Developer Portal app in Teams web browser and Teams Developer Portal refers same repogitory. The Developer Portal app in Teams desktop app refers "App Studio" repository. I think "App Studio" is currently deprecated and it doesn't support the latest manifest version. But The Developer Portal app uses latest manifest version. Is it the reason that causes error?"Manifest parsing has failed." in Developer Portal
I am using the Developer Portal app in Teams. I got "Manifest parsing has failed." error when click "Preview in Teams" button. Also I got "App does not have the required permissions for this operation." error after click "x" button. I have no validation error in the manifest file. How can I fix it?
