Giter Site home page Giter Site logo

officedev / microsoft-teams-apps-newemployeeonboarding Goto Github PK

View Code? Open in Web Editor NEW
69.0 17.0 40.0 661 KB

New Employee Onboarding(NEO) enables your organization to connect new employees to people & culture and provide them with consistent experience and information to be productive faster. Built with Sharepoint New Employee Onboarding solution as a backend with deep integration in Teams, NEO app makes it super easy for learning teams/ Human resources to manage relevant content and process for new employees using sharepoint lists. HR teams can also configure the time for an employee to be a new hire ex. 90 days and the app will stop notifying the new hires after that window. The new hire checklist is integrated into the NEO Teams app and is used to guide the new hire through the onboarding journey. The checklist can be corporate or departmental. Additionally, new hires can also introduce themselves using the app by sharing an introduction which is automatically shared with their managers. This automation makes it easier for managers to review introductions about all new hires and share them with the relevant teams in one shot! At any time, new employees can share feedback on a task in their onboarding journey or on the overall experience using a helpful bot command. All feedback is shared with HR team through helpful notifications and can be downloaded. Moreover, HR teams can also use the app to share pulse surveys for new employees at a configurable frequency.

License: MIT License

C# 90.15% CSS 1.57% JavaScript 1.44% HTML 0.66% TypeScript 5.67% Batchfile 0.50%

microsoft-teams-apps-newemployeeonboarding's Issues

New Employee Onboarding App is not Microsoft published

Hi,

We are getting the following confirmation message when trying to install the NEO template. The message here says that the app is not published by Microsoft that concerns Me and our client. Can you please look into it as soon as possible.
image

Thanks
Amit

NEO Bot Azure Table Storage CreateIfNotExists failure

Hi,

As per the code, any table should be created automatically before query/insert/update because I can see the code for InitializeAsync from BaseStorageProvider is called every time. This fails and as a result, the Bot fails in the following scenario.

  1. Uninstall NEO Bot from the MS Teams client.
  2. Go to Azure Table Storage and delete UserConfiguration table.
  3. Install NEO Bot on the MS Teams client again.
  4. After installing a welcome message should appear and user details should be stored in UserConfiguration table, this fails because it fails to create UserConfiguration table even though the code is there.
  5. I also observe the same happens with TeamConfiguration table.

My team and I are working on one of our clients and need to have the solution for this to expand this bot's functionality as per our requirement.

Thanks
Amit Gaonkar

Deployment /Failed for Microsoft.Web/serverfarms

I have encountered the following error during deployment.

{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"message":"This region has quota of 0 instances for your subscription. Try selecting different region or SKU."}]}

I had selected North Central US based on the products by region info and the required services. Hopefully this was a correct region.

My subscription is a Trial Subscription in an E5 developer tenant.

Please advise what steps are necessary to rectify the issue.

Thanks in advance!
Lou

<BotError>Bot returned unsuccessful status code NotImplemented

Hello, any ideas why the bot returns <BotError>Bot returned unsuccessful status code NotImplemented after clicking "Introduce yourself" in Teams? HTTP 502 is the response code to the "invoke" request. It shows "Unable to reach app. Please try again" for the user. Please see screenshot below:

image

Bot not responding

Hi Community,
The app has been uploaded and I could see the new employee checklist in the tab but the bot is not responding on the commands. Is there any way that I can fix this?

Something went wrong

I followed the whole deployment process and had no issues. When I want to install the app in Teams however, I get the error message "Something went wrong"

Which is not helpful at all

image

The package manifest run through without any errors, so I guess the issues can't be in the manifest, right?

I have no idea where to look

Signin Error

Hello,
User is facing the below issue while accessing the app.
NEO error

How should this be resolved and what is causing this issue?

Viewing Weekly Plan

Hello. Any ideas on how to configure or set up the weekly plan ? I keep getting a message that my plan is not available right now. Any insights would be appreciated.

Bot doesn't reply in Teams, nor does it in Web Chat (test mode)

Hey,

I followed the deployment guide verbatem but unfortunately the bot doesn't reply. The logs show exceptions with the message as shown in the printscreen.

image

The details of the log item are as followed
image
image

Hopefully someone is able to provide me with some guidance.

Thanks!

Cannot find Option in Deployment Guide on Azure Portal

Hello,

I am working through the deployment guide to deploy the New Employee Onboarding App for my organisation but I have hit a block.

On Step 6, number 3, I don't seem to see the Add Setting option under the Settings options as stated. Grateful if you can point me in the right direction.

I have attached screenshots if that helps

Azure Bot_DocScreen

Azure Bot_PortalScreen

Feedback function not working

Hello Team while I was able to deploy the solution, I continue to see the Feedback functionality(it goes on loop for sign-in) not working in the NEO app. Is this a bug?

Build Failed | Beta Graph API to fetch user profile note is failing

Build Failed, following error is found in log under App Service > Deployment Center > logs-

"Build Failed:

Following error in log:

[email protected] build D:\home\site\repository\Source\Microsoft.Teams.Apps.NewHireOnboarding\ClientApp
react-scripts build

Creating an optimized production build...
Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db

Why you should do it regularly:
https://github.com/browserslist/browserslist#browsers-data-updating
node D:\home\site\repository\Source\Microsoft.Teams.Apps.NewHireOnboarding\ClientApp\node_modules\react-scripts\scripts\build.js[8632]: c:\ws\src\env-inl.h:957: Assertion (ret) != (nullptr)' failed. npm ERR! code ELIFECYCLE npm ERR! errno 134 npm ERR! [email protected] build: react-scripts build`
npm ERR! Exit status 134
npm ERR!
npm ERR! Failed at the [email protected] build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! D:\local\AppData\npm-cache_logs\2021-04-23T13_12_13_639Z-debug.log
D:\home\site\repository\Source\Microsoft.Teams.Apps.NewHireOnboarding\Microsoft.Teams.Apps.NewHireOnboarding.csproj(168,3): error MSB3073: The command "npm run build" exited with code 134.
Done Building Project "D:\home\site\repository\Source\Microsoft.Teams.Apps.NewHireOnboarding\Microsoft.Teams.Apps.NewHireOnboarding.csproj" (default targets) -- FAILED.

Build FAILED."

Also tried following -
i) Failed after redeploy.
ii) I have deleted node_modules manually and redeploy, still failed

Find the full log -
redeply_app_service_2.txt

image

Issue when deploying manifest

When deploying the app manifest towards my teams admin center app catalog or through the teams app developer portal. I get the following error:
image

I have already tried adding the properties through the dev portal or by manually adding them to the manifest but with no success...

Does anyone have any idea how to fix this issue?

My manifest looks like this:

{
"$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.5/MicrosoftTeams.schema.json",
"manifestVersion": "1.5",
"version": "1.0.0",
"id": "1c412988-ba71-40af-8b9b-b5be27fe3a6f",
"packageName": "com.microsoft.teams.newemployeeonboarding",
"developer": {
"name": "Imec",
"websiteUrl": "REMOVED",
"privacyUrl": "REMOVED",
"termsOfUseUrl": "REMOVED"
},
"localizationInfo": {
"defaultLanguageTag": "en",
"additionalLanguages": [
{
"languageTag": "en-US",
"file": "en-US.json"
}
]
},
"icons": {
"color": "color.png",
"outline": "outline.png"
},
"name": {
"short": "New Employee Onboarding",
"full": "New Employee Onboarding"
},
"description": {
"short": "New employee on boarding app will simplify employee on boarding",
"full": "New employee on boarding app will simplify the new employee on boarding using MS Teams and SharePoint Online. NEO bot will be created to cater to below requirements."
},
"accentColor": "#7BFFFE",
"bots": [
{
"botId": "1fc8aa96-b73a-40c7-92e9-d8360b29122d",
"scopes": [
"personal",
"team"
],
"commandLists": [
{
"scopes": [
"personal"
],
"commands": [
{
"title": "New employee checklist",
"description": "View your learning path"
},
{
"title": "Share feedback",
"description": "Submit an idea or feedback"
},
{
"title": "Review introductions",
"description": "Review employee intros"
},
{
"title": "Help",
"description": "Take a tour"
}
]
}
],
"supportsFiles": false,
"isNotificationOnly": false
}
],
"staticTabs": [
{
"entityId": "Journey",
"name": "New employee checklist",
"contentUrl": "REMOVED",
"scopes": [
"personal"
]
}
],
"configurableTabs": [
{
"configurationUrl": "REMOVED",
"canUpdateConfiguration": true,
"scopes": [
"team"
]
}
],
"validDomains": [
"REMOVED",
"token.botframework.com",
"REMOVED"
],
"webApplicationInfo": {
"id": "1fc8aa96-b73a-40c7-92e9-d8360b29122d",
"resource": "REMOVED"
}
}

Teams Bot - Something went wrong. Try again in a few minutes.

Deploying this new app as a test before we try in a live environment and having issues with the bot in teams getting the error - Something went wrong. Try again in a few minutes.

This is for a brand new user just added as a test so the automated flow is working as the message appears on its own but not the correct content. I don't believe I have done anything wrong, deleted and re-created this twice and same error in Teams so what can i do to further fault find this?

image

Kind Regards

Jack Summers

Issue running application after install

Now that we've successfully deployed the application in our environment, we're starting to test and setup the different areas. In a preliminary test where the users is asked to Introduce themselves we do get a pop up window, however the window is blank!
NewHireScreenshot blank
See attached. What are doing wrong? We've double checked all the configurations in the app to make sure they're pointing to the correct places.
Do you offer paid support? We'd be happy to pay to get this up and running.

Thanks
Brendan

ARM template - Unable to install

I tried installing the template but run into issues cpomplainibg that of 0 instances for your subscruption. I have ample Azure credits, tried several location but still the issue doesn't go away. Can't seem to deploy the template. Any help would be appreciated.

image

Error below -
{"code":"InvalidTemplateDeployment","details":[{"code":"ValidationForResourceFailed","message":"Validation failed for a resource. Check 'Error.Details[0]' for more information.","details":[{"code":"SubscriptionIsOverQuotaForSku","message":"This region has quota of 0 instances for your subscription. Try selecting different region or SKU."}]}],"message":"The template deployment 'Microsoft.Template-20221212104707' is not valid according to the validation procedure. The tracking id is '117944fa-911a-4773-9c58-a5d7b2d0f2e6'. See inner errors for details."}

SSO doesn't work with SharePoint List in Teams tab

After the solution is deployed and when the user tries to access the New Employee Checklist from the Teams tab app, nothing happens.
It is expected that the user is authenticated and access the SharePoint List content directly within the MS Teams tab app

On Teams web client, the user needs to be authenticated on SPO first - In that case, he can access the content from the Teams tab - This is due to the authent cookie from the SPO connection being reused in the context of Teams.

On the desktop / mobile client, the authentication flow is not trigger and nothing happens.

Based on the description of this app, the user should be able to access SharePoint from MS Teams tab

The deployment guide does not which are the resources getting created in the resource group after the deployment

The deployment guide does not specify the complete set of resources which get created after deploying this ARM template. The developer deploying this template needs to inspect the ARM JSON in order to understand what's getting created. I find it nice to have in the guide:

  • an explanation with all the resources which get deployed,
  • the naming requirements for each resource
  • and the purpose of each resource.

Thank you.

App Template Deploy always fails in Build Stage

I've been trying to deploy the New Employee Onboarding Teams app template available here https://aka.ms/teamsapptemplates, but this always fails.

image

image
{

"status": "Failed",

"error": {

    "code": "ResourceDeploymentFailure",

    "message": "The resource operation completed with terminal provisioning state 'Failed'."

}

}

Tried to redeploy the source controls several times on the app service - fails on build all the time -

C:\home\site\repository\Source\Microsoft.Teams.Apps.NewHireOnboarding\ClientApp\node_modules\react-scripts\scripts\build.js[6100]: c:\ws\src\env-inl.h:957: Assertion (ret) != (nullptr)' failed. npm ERR! code ELIFECYCLE npm ERR! errno 134 npm ERR! [email protected] build: react-scripts build`
npm ERR! Exit status 134
npm ERR!
npm ERR! Failed at the [email protected] build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\local\AppData\npm-cache_logs\2021-08-10T10_41_25_551Z-debug.log
C:\home\site\repository\Source\Microsoft.Teams.Apps.NewHireOnboarding\Microsoft.Teams.Apps.NewHireOnboarding.csproj(168,3): error MSB3073: The command "npm run build" exited with code 134.
Done Building Project "C:\home\site\repository\Source\Microsoft.Teams.Apps.NewHireOnboarding\Microsoft.Teams.Apps.NewHireOnboarding.csproj" (default targets) -- FAILED.

Build FAILED.

"C:\home\site\repository\Source\Microsoft.Teams.Apps.NewHireOnboarding\Microsoft.Teams.Apps.NewHireOnboarding.csproj" (default target) (1:7) ->
(PublishRunWebpack target) ->
C:\home\site\repository\Source\Microsoft.Teams.Apps.NewHireOnboarding\Microsoft.Teams.Apps.NewHireOnboarding.csproj(168,3): error MSB3073: The command "npm run build" exited with code 134.

0 Warning(s)
1 Error(s)

Bot asks for credentials.

I was able to successfully get the app template deployed in Azure and deploy the teams app. Unfortunately, nothing seems to be working any I’m not sure how to identify what the issue is. The onboarding bot just responds with “Something went wrong. Try again in a few minutes.” It also is asking for users to sign in. Any ideas what might cause this behavior and how I can go about troubleshooting it?

Redirect.tsx file is vulnerable to XSS

Vulnerability Name : XSS - Cross Site Scripting
Impact: Sending unvalidated data to a web browser can result in the client/browser executing malicious code.
Vulnerable File Location: Source/Microsoft.Teams.Apps.NewHireOnboarding/ClientApp/src/components/redirect.tsx
File Name: redirect.tsx
Line No# 17

Troubleshooting Tips + Documentation Clarification

Below are updates to the documentations and clarifications on few steps during deployment:

1. Configuring SharePoint

The new lookbook URL is https://lookbook.microsoft.com/details/388a159f-475b-4557-9088-c9073a26c576. After deploying the site, continue with adding in a question to the NewHireQuestionnaire and verify that the New Hire Checklist has the required columns as described in the SharePoint Configuration guide

2. Setting up users and managers in test tenant

If you are using a test tenant, please make sure that all test users have the correct managers assigned. New Employee Onboarding uses the User Details in AAD to determine whether someone is a New Hire or a Manager. You can set up your tenant users through Azure Portal > Azure Active Directory > Users

3. Deploying ARM Template

When deploying the template, we recommend the following:

  • Base Resource Name should be less than 19 as the KeyVault should be less than 24 characters and the ARM template naming for KeyVault is "{base resource name}vault"
  • Suggest that Base Resource Name be given in all lower cases to prevent case sensitivity in future applications
  • Human Resource Link must be a team and not a channel. To get Team link, refer to the below screenshot:image
  • SharePoint tenant name should be in the form of *****.sharepoint.com

4. Verify Deployment Status

Before uploading the manifest to Teams, check the deployment status (steps below):

  1. Go to Azure Portal and navigate to the Resource Group
  2. Click on the Deployments:
    image
  3. If the deployment completed with the terminal provisioning state "Failed", then you will need to re-sync deployment. The transitive dependency set of the front-end web app pulls in over 1,000 NPM packages, and sometimes there is an error fetching all of the packages. To fix, please do the following:
  4. Go to the "Deployment center" section of the app service that failed to deploy.
  5. Click on "Sync" to restart the deployment.
    image

5. Failing to Sync Multiple Times

If you are continuously unsuccessful with syncing your deployment from Section 4, you will need to delete the node_modules folder and try syncing again:

  1. On Azure Portal, open the app service
  2. Click on the url provided (https://******.azurewebsites.net)
  3. Add .scm to the URL (https://******.scm.azurewebsites.net)
  4. Click on "Debug Console" on the top menu then "CMD"
  5. Navigate to Site > repository > Source > Microsoft.Teams.Apps.NewHireOnboarding > ClientApp
  6. Delete "node_modules" folder or rename it to "node_modules_old"
  7. Retry syncing the deployment again as described in Section 4

Introduce Yourself pop up is empty

The "Say Hello to NEO" card displays with all options to Introduce yourself, Take a Tour, and View weekly Plan.
The bot responds when clicked on Introduce Yourself, with a pop-up window titled New Employee Onboarding that is empty.

The SharePoint list with the intro questions has been populated.

I need help with troubleshooting why the Introduce Yourself pop-up is empty, nothing is displayed.

"Review introductions" from bot commands do not work and don't access feedback tab

Hi everyone ı have two question;

I installed NEO apps but when I click on the review introductions, something like this
it outputs => There are no intros for you to review right now.

And the other question;
I installed an onboarding application in the team
but when I say sign in in the feedback section,
a page is not opening,

In a short, "review introductions" from bot commands do not work.
Secondly, I cannot access the feedback section in the team.

What is the solution for these two errors, thank you.

Error deploying the solution in Azure (App Service)

After performing the previous steps indicated in the installation guide, when deploying the NEO solution in Azure, I receive this error:

ErrorProv

{ "code": "DeploymentFailed", "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.", "details": [ { "code": "Conflict", "message": "{\r\n \"status\": \"Failed\",\r\n \"error\": {\r\n \"code\": \"ResourceDeploymentFailure\",\r\n \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\"\r\n }\r\n}" } ] }

I think it can be a problem when trying to download many packages or frameworks that use the web solution, this takes a lot of time and gives an error.

The template does not specify the name of the azure key vault should be shorter

I was trying to deploy this template and the deployment failed with this error:
{

"status": "Failed",
"error": {
    "code": "VaultNameNotValid",
    "message": "The vault name 'BrusselsNewEmployeeOnBoardingvault' is invalid. A vault's name must be between 3-24 alphanumeric characters. The name must begin with a letter, end with a letter or digit, and not contain consecutive hyphens. Follow this link for more information: https://go.microsoft.com/fwlink/?linkid=2147742"

}

}

I find it more intuitive to specify this constraint in the deployment guide itself, rather than making the developer search for the error, then find the official docs:
https://docs.microsoft.com/en-us/azure/key-vault/general/quick-create-cli#create-a-key-vault:

"Key vault name: A string of 3 to 24 characters that can contain only numbers (0-9), letters (a-z, A-Z), and hyphens (-)"

That would save time for the developers trying to deploy the template. Thank you!

Something went wrong. Try again in a few minutes.

Encountering two errors in Teams app:

  1. Something went wrong. Try again in a few minutes.
  2. Clicking 'Take a tour' or 'Review introductions' button errors out with "Unable to reach app. Please try again."

image

NEO Bot UserConfiguration Conversation Id is getting empty

Hi,
There is a major bug with the conversation id getting empty even for users who have installed the bot. This is resulting in the failure to send automated notifications to Bot users.
I found that class AppManagerBackgroundService method SyncUsersFromSecurityGroupAsync updates UserConfiguration table with AadObjectId and conversation id as empty for all the users including users who already have bot installed.
See screen shot for the exact line of code
image

Thanks
Amit Gaonkar

adding to Teams Channel as a Tab - failure

When I try to add the app as tab to the existing Teams channel, getting below exceptions, any insight would be grateful.

"The resource you are looking for has been removed, had its name changed, or is temporarily unavailable."

error.pdf
image

Bot error

error

I have error "unable to reach app. Please try again" and the bot responds with "something went wrong. Try again in a few minutes" every time I click on "introduce yourself"; although I have added the "token.botframework.com" in the valid domains.

Moreover, when user clicks on the sign-in button, it gives the error "The Sign In code was not found or expired. Please try asking the bot to sign in again."

In the application insights shows error "Microsoft.IdentityModel.Tokens.SecurityTokenSignatureKeyNotFoundException".

Anyone know what the issue here is and how to fix?

Please Sign in > Authentication Failure

While in the bot on Team, I clicked the sign in and got this message:

image

On Azure Portal for the bot, I saw this

image

Here is the End-to-End Transaction details

image

This is the call stack:

Microsoft.IdentityModel.Tokens.SecurityTokenSignatureKeyNotFoundException:
at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateSignature (System.IdentityModel.Tokens.Jwt, Version=5.6.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35)
at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateToken (System.IdentityModel.Tokens.Jwt, Version=5.6.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35)
at Microsoft.AspNetCore.Authentication.JwtBearer.JwtBearerHandler+d__6.MoveNext (Microsoft.AspNetCore.Authentication.JwtBearer, Version=3.1.7.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)

Introduce Yourself pop up is empty / View Weekly Plan throws error message

The "Say Hello to NEO" card displays with all options to Introduce yourself, Take a Tour, and View weekly Plan.
The bot responds when clicked on the option to View Weekly Plan, with "Your complete plan is not available right now"
The bot responds when clicked on Introduce Yourself, with a pop-up window titled New Employee Onboarding that is empty, white.
Take a Tour seems to be the only functionality working; I can submit feedback, I can see the new hire checklist in a tab from teams, but again, I cannot introduce myself as the pop up is empty.

The SharePoint list with the intro questions has been populated.
I can see all the Feedback submitted from different users in a table from a teams tab, with the option to download. Seems that is working fine.

I need help with troubleshooting why the Introduce Yourself pop-up is empty, nothing is displayed, and with the feature View Weekly Plan error message.

New Employee Checklist blank and Bot not responding

Hello,

I am having some issues after deploying the ARM and having the app uploaded to Teams without error. The bot does not respond to any of the commands. Also when I look at New Employee Checklist the page is just blank. Another thing I found was when I wanted to add the bot to a Team the window that pops up is also blank and I can not add the bot to the Teams.

Images below of each issue.

Bot not responding:
image

New employee check list blank:
image

Can't add to a Team:
image

I've checked other issues and they didn't seem to fit the same bill. Any help would be appreciated.

Error with the introduce yourself feature

Post troubleshooting I was able to deploy the solution but the App doesn't work completely. Facing the issue with 'Introduce yourself'. I see the app insights record several instances of
:_IDX10501: Signature validation failed. Unable to match key: kid: '[PII is hidden. For more details, see https://aka.ms/IdentityModel/PII.]'. Exceptions caught: '[PII is hidden.

Azure deployment fails same place each attempt

"statusCode": "Conflict",
"statusMessage": {
"status": "Failed",
"error": {
"code": "ResourceDeploymentFailure",
"message": "The resource operation completed with terminal provisioning state 'Failed'."
}
},
"targetResource": {
"id": "/subscriptions/subid/resourceGroups/Teams-App-Templates-POC/providers/Microsoft.Web/sites/NEO/sourcecontrols/web",
"resourceType": "Microsoft.Web/sites/sourcecontrols",
"resourceName": "NEO/web"

Problem creating App Service

The app framework is dotnet3.1 but the only two options in Azure App Service are .net 6 LTS and .net 7 STS, how it must be handled?.

Regards

Joe

Error once app installed

Have encountered several issues while installing the app template.
First trying to install it in a Teams Channel server IP address could not be found.
While trying to talk with the bot, error message and an authentication button but clicking on it doesn't do anything.
Screenshot 2020-11-16 204839
Screenshot 2020-11-16 204846

Bot is not responding

I just recently deployed the NEO. However the bot is not responding. I tested on the web app in Azure and no responses are given there.
I see this error on the Channels:

image
"There was an error sending a message to your bot: HTTP status code not found.

"Something went wrong. Try again in a few minutes" error

I have followed the deployment guide four times, without a successful deployment of this solution. Each time I deploy, go into the "test in web chat" or sideload into Teams and (in both locations) get a "Something went wrong. Try again in a few minutes" error message from the bot. Any thoughts on why this is occurring?

Sign-in prompt doesn't follow the bot design guideline

There is a serious design issue:

  • When user first installs the app, the bot sends a prompt to user to sign-in
  • ->If user clicks on the "Sign-in" button and fails to authenticate on the first try:
  • ----> The same button no longer works saying "The Sign In code was not found or expired. Please try asking the bot to sign in again."
  • ---->The bot never send another prompt to sign-in if the previous attempt fails
  • ----> If the user tries to use a functionality that requires users' identity (which is most of the app), the auth. fails and it never send another sign-in request. : Signature validation failed. Unable to match key
  • Microsoft.IdentityModel.Tokens.SecurityTokenSignatureKeyNotFoundException: at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateSignature (System.IdentityModel.Tokens.Jwt, Version=5.6.0.0, Culture=neutral, PublicKeyToken=XXXXXXXXXX) at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateToken (System.IdentityModel.Tokens.Jwt, Version=5.6.0.0, Culture=neutral, PublicKeyToken=XXXXXXXXXX) at Microsoft.AspNetCore.Authentication.JwtBearer.JwtBearerHandler+<HandleAuthenticateAsync>d__6.MoveNext (Microsoft.AspNetCore.Authentication.JwtBearer, Version=3.1.7.0, Culture=neutral, PublicKeyToken=XXXXXXXXXX)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.