Skip to content
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

Open
petrbroz opened this issue Nov 26, 2024 · 5 comments
Open

[Question] how to authenticate the rag-extension? #8

petrbroz opened this issue Nov 26, 2024 · 5 comments
Labels
question Further information is requested

Comments

@petrbroz
Copy link

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:

  1. I go to https://github.com/copilot
  2. I @ the extension and ask it a question
  3. I get the Connect with <extension name> prompt
  4. I go through the OAuth workflow
  5. I'm redirected to <FQDN>/auth/callback, and I get the All done! Please return to the app message

However, 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!

@petrbroz petrbroz added the question Further information is requested label Nov 26, 2024
@theodoracheng
Copy link
Collaborator

@petrbroz Do you mind sharing a screenshot? You should be able to @ your extension in your chat after authorizing

@petrbroz
Copy link
Author

petrbroz commented Dec 5, 2024

Hi @theodoracheng, I've tried one more time. Here's the steps I took, incl. screenshots:

Step 1: I ask @rag-copilot-extension-test a question
Image

Step 2: I'm prompted to connect my GitHub account
Image

Step 3: I authorize the application
Image

Step 4: I'm redirected back to a message saying "All done! Please return to the app"
Image

Step 5: in the GitHub chat I still see the prompt to connect my GitHub account
Image

Step 6: after closing the prompt, I get a message saying "I was unable to connect you to because you cancelled the authentication"
Image

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:
Image

So the bottom line is: I can no longer reproduce the issue I had last week.

@petrbroz
Copy link
Author

petrbroz commented Dec 5, 2024

Would it be possible to update the workflow so that (in step 6) the chat confirms that the application was connected successfully?

@belaltaher8
Copy link
Collaborator

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!

@ChrisCarini
Copy link

I just ran into the same thing - any updates here on an improved UX with more clarity?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants