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

Cookies and Auth_Key #3

Open
elbiozard opened this issue May 11, 2023 · 5 comments
Open

Cookies and Auth_Key #3

elbiozard opened this issue May 11, 2023 · 5 comments

Comments

@elbiozard
Copy link

Hello, is it still working? I can't find the AUTH_KEY in Cookies

@izdrail
Copy link

izdrail commented May 12, 2023

@elbiozard I've just removed that check and rebuild the image
just comment from 16 -> 21 line and you should have it working in main.py
I guess he is using that to check if from a third party service or something

@hussainwali74
Copy link

not working am using these:
__Secure-1PSID
SID

@izdrail
Copy link

izdrail commented May 12, 2023

I've told you you need to comment or remove the lines and the post to /ask
{ 'session_id': "THE __SECURE-1PSID", "message": "Your bard question" }

@ra83205
Copy link
Owner

ra83205 commented May 12, 2023

Hello, is it still working? I can't find the AUTH_KEY in Cookies

Hello! I noticed that the attribute AUTH_KEY, which has been renamed to USER_AUTH_KEY, is causing some confusion for people, and I would like to clarify its purpose. The value of USER_AUTH_KEY is essential for ensuring that your API endpoint has at least some minimal protection and is not directly linked to Bard. Initially, we required this parameter for all API requests, but now USER_AUTH_KEY is an optional parameter.

To send a POST request to the API, you will need to include the session ID in the request body along with the message prompt. The session ID is the value of the __SECURE-1PSID cookie, which you can retrieve from the user's browser.

Therefore, you can update this repository to reflect the new changes.

@raymerjacque
Copy link

you should have the session_ID server side, not client side. its dangerous to have it client side.

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

No branches or pull requests

5 participants