-
Notifications
You must be signed in to change notification settings - Fork 8
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
[Question] how to authenticate the rag-extension? #8
Comments
@petrbroz Do you mind sharing a screenshot? You should be able to @ your extension in your chat after authorizing |
Hi @theodoracheng, I've tried one more time. Here's the steps I took, incl. screenshots: Step 1: I ask Step 2: I'm prompted to connect my GitHub account Step 3: I authorize the application Step 4: I'm redirected back to a message saying "All done! Please return to the app" Step 5: in the GitHub chat I still see the prompt to connect my GitHub account Step 6: after closing the prompt, I get a message saying "I was unable to connect you to because you cancelled the authentication" Now, when I got to this point last week, I tried asking the Copilot again, and I didn't get any answer. However, when I asked Copilot today, it did respond: So the bottom line is: I can no longer reproduce the issue I had last week. |
Would it be possible to update the workflow so that (in step 6) the chat confirms that the application was connected successfully? |
hey @petrbroz 👋🏼 that's a great call out! Seems like you were already authorized, but because you exited out of the authorization prompt it complained that it couldn't connect. We will file an issue to return a more appropriate message there to indicate whether you're actually authorized or not! |
I just ran into the same thing - any updates here on an improved UX with more clarity? |
Question
How exactly does one authenticate the rag-extension?
Context
I'm trying to run the rag-extension sample locally. I've followed the steps in the README, and this is how far I can get:
@
the extension and ask it a questionConnect with <extension name>
prompt<FQDN>/auth/callback
, and I get theAll done! Please return to the app
messageHowever, when I go back to the conversation, I still see the same
Connect with <extension name>
prompt. What exactly is supposed to happen after this step? Am I missing something?Thanks!
The text was updated successfully, but these errors were encountered: