botAadApp/create failed: CredentialInvalidLifetimeAsPerAppPolicy

[ross-p-smith]

Describe the bug
When I Provision an application it fails

  (×) Error: botAadApp/create failed.
    (×) Error: A http client error happened while performing the botAadApp/create task. The error response is: {"error":{"code":"CredentialInvalidLifetimeAsPerAppPolicy","message":"Credential lifetime exceeds the max value allowed as per assigned policy 'aaaaaaa'.","details":[{"code":"InvalidKeyEndDate","message":"Credential lifetime exceeds the max value allowed as per assigned policy 'aaaaaa'.","target":"EndDate"}],"innerError":{"date":"2024-03-05T13:14:55","request-id":"xxxx","client-request-id":"xxxx"}}}

Expected behavior
Documentation should tell me how to set the Credential Lifetime or how to set this up manually

VS Code Extension Information (please complete the following information):

• OS: WSL
• Version latest

[microsoft-github-policy-service]

Thank you for contacting us! Any issue or feedback from you is quite important to us. We will do our best to fully respond to your issue as soon as possible. Sometimes additional investigations may be needed, we will usually get back to you within 2 days by adding comments to this issue. Please stay tuned.

[blackchoey]

@ross-p-smith We're working to support setting customized credential lifetime for you application. For now, please follow Use an existing Microsoft Entra app for your bot to create an app by yourself and use it in your project.

[blackchoey]

The latest Teams Toolkit is able to set customized credential lifetime via aadApp/create action now. Please have a try and let us know if you have further questions.

[microsoft-github-policy-service]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

[microsoft-github-policy-service]

Due to lack of details for further investigation, we will archive the issue for now. In case you still have following-up questions on this issue, please always feel free to reopen the issue by clicking ‘reopen issue’ button below the comment box. We will get back to you as soon as possible.