-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSO Implementation #12559
Comments
As long as you configured the Entra app registration as multi-tenant, it should work. Please share the error message if you meet any issues. |
index.ts File: import * as restify from "restify"; const credentialsFactory = new ConfigurationServiceClientCredentialFactory({ const botFrameworkAuthentication = new ConfigurationBotFrameworkAuthentication( const adapter = new CloudAdapter(botFrameworkAuthentication); const onTurnErrorHandler = async (context: TurnContext, error: Error) => { if (context.activity.type === "message") { adapter.onTurnError = onTurnErrorHandler; const memoryStorage = new MemoryStorage(); const conversationState = new ConversationState(memoryStorage); const bot = new TeamsBot(conversationState, userState); const server = restify.createServer(); server.post("/api/messages", async (req, res) => { ..................................... import { export class TeamsBot extends TeamsActivityHandler { private conversationState: ConversationState; constructor(conversationState: ConversationState, userState: UserState) {
} private async promptForLoginStep(step: WaterfallStepContext) {
} private async processLoginResultStep(step: WaterfallStepContext) {
} } I’m facing an issue with the package I am using. It keeps returning errors indicating that certain functionality is not present in the package. I believe the botbuilder package might have been updated, and I am looking for the correct package that supports Single Sign-On (SSO) and allows retrieval of an access token with user context. Could you please provide guidance on the latest package version I should use to enable SSO and obtain an access token with the user's context in a Teams bot application? |
You could refer this sample for implementation details: https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/bot-conversation-sso-quickstart/js |
i am refering to https://github.com/OfficeDev/Microsoft-Teams-Samples/blob/main/samples/bot-sso-adaptivecard/nodejs/bots/botSSOAdaptiveCard.js, Don't we have getSignInLink method on the adapter object in the current version? |
@arundhathiMenon To get better support, could you please create an issue in the Microsoft-Teams-Samples repo asking them to update the sample code? You could also create an issue in the botbuilder package's repo for help: https://github.com/microsoft/botbuilder-js. |
can you please guide me on this,
I have two accounts: [email protected] and [email protected]. On Azure, I have a subscription under the one.ai tenant, where I’ve registered both an app and a bot. However, I have a SharePoint license and a Microsoft Teams account associated with the [email protected] account.
Currently, I’m implementing SSO (Single Sign-On) to authorize users when they log in to Microsoft Teams, but I am using the app registration credentials (client ID, secret, etc.) from the [email protected] tenant.
Will this setup work, or is there a requirement to have a subscription under the two.ai tenant as well for proper SSO functionality? Would having the app and bot registered under two.ai be necessary for this scenario?
The text was updated successfully, but these errors were encountered: