-
Notifications
You must be signed in to change notification settings - Fork 1
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
does not work locally or when deployed to cloudflare #3
Comments
Thanks! Deployment via Cloudflare should work. I haven't updated the README yet, but you need a I also have troubles with local hosting as the calls between frontend and backend fail. I added a |
I recommend you check the application logs with |
Will do.
…On Wed, May 10, 2023 at 12:24 PM Paul Haedrich ***@***.***> wrote:
I recommend you check the application logs with npx wrangler tail, any
errors should pop up there
—
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEVLYDWKSSW6GZTM7EW223XFPFLLANCNFSM6AAAAAAX5AIVZQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I suspect that the local dev will need self-signed certs since the passkey
spec requires ssl.
…On Wed, May 10, 2023 at 12:26 PM Steven Endres ***@***.***> wrote:
Will do.
On Wed, May 10, 2023 at 12:24 PM Paul Haedrich ***@***.***>
wrote:
> I recommend you check the application logs with npx wrangler tail, any
> errors should pop up there
>
> —
> Reply to this email directly, view it on GitHub
> <#3 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAEVLYDWKSSW6GZTM7EW223XFPFLLANCNFSM6AAAAAAX5AIVZQ>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
Good idea! That might be it! |
FYI. This example worker works on localhost using http:
https://github.com/worker-tools/webauthn-example
…On Wed, May 10, 2023 at 1:30 PM Paul Haedrich ***@***.***> wrote:
I suspect that the local dev will need self-signed certs since the passkey
spec requires ssl.
Good idea! That might be it!
—
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEVLYCWCG5H2QCL5TGK2RTXFPGEDANCNFSM6AAAAAAX5AIVZQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Any luck getting it working on a live Worker? |
I was able to get a simple version that works locally and live(custom
domain) last night. I followed the instructions for setting up the domain
and the certificate for ssl here:
https://simplewebauthn.dev/docs/advanced/example-project
I'll apply what I learned to your worker next.
…On Sat, May 13, 2023 at 8:59 AM Paul Haedrich ***@***.***> wrote:
Any luck getting it working on a live Worker?
—
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEVLYAE7DFMKGPOEJCXVSLXF6ASVANCNFSM6AAAAAAX5AIVZQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Hi Paul,
I put a version on cloudflare at passkeys-demo.urstp.io for you to see the
errors I am receiving using your demo. This site is the best way for me to
communicate with you about the errors. I have no interest in hosting a demo
any longer than it takes to debug the webauthn problems and will take it
down once we have worked through the issues. I removed your logo and left
your disclaimer in the html.
Here is a screen shot of the errors I face. You should be able to recreate
these in your own browser.
[image: image.png]
…On Sat, May 13, 2023 at 9:17 AM Steven Endres ***@***.***> wrote:
I was able to get a simple version that works locally and live(custom
domain) last night. I followed the instructions for setting up the domain
and the certificate for ssl here:
https://simplewebauthn.dev/docs/advanced/example-project
I'll apply what I learned to your worker next.
On Sat, May 13, 2023 at 8:59 AM Paul Haedrich ***@***.***>
wrote:
> Any luck getting it working on a live Worker?
>
> —
> Reply to this email directly, view it on GitHub
> <#3 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAEVLYAE7DFMKGPOEJCXVSLXF6ASVANCNFSM6AAAAAAX5AIVZQ>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
I am investigating the jwt string in dev.vars.
…On Sat, May 27, 2023 at 8:06 AM Steven Endres ***@***.***> wrote:
Hi Paul,
I put a version on cloudflare at passkeys-demo.urstp.io for you to see
the errors I am receiving using your demo. This site is the best way for me
to communicate with you about the errors. I have no interest in hosting a
demo any longer than it takes to debug the webauthn problems and will take
it down once we have worked through the issues. I removed your logo and
left your disclaimer in the html.
Here is a screen shot of the errors I face. You should be able to recreate
these in your own browser.
[image: image.png]
On Sat, May 13, 2023 at 9:17 AM Steven Endres ***@***.***> wrote:
> I was able to get a simple version that works locally and live(custom
> domain) last night. I followed the instructions for setting up the domain
> and the certificate for ssl here:
>
> https://simplewebauthn.dev/docs/advanced/example-project
>
> I'll apply what I learned to your worker next.
>
> On Sat, May 13, 2023 at 8:59 AM Paul Haedrich ***@***.***>
> wrote:
>
>> Any luck getting it working on a live Worker?
>>
>> —
>> Reply to this email directly, view it on GitHub
>> <#3 (comment)>,
>> or unsubscribe
>> <https://github.com/notifications/unsubscribe-auth/AAEVLYAE7DFMKGPOEJCXVSLXF6ASVANCNFSM6AAAAAAX5AIVZQ>
>> .
>> You are receiving this because you authored the thread.Message ID:
>> ***@***.***>
>>
>
|
Adding the following lines to my wrangler.toml file got it to work:
[vars]
# I used a 16 char random string
JWT_TOKEN = "some simple string"
node_compat = false
# Override values for `--env staging` usage
[env.staging]
workers_dev = false
JWT_TOKEN = "staging random string"
# Override values for `--env production` usage
[env.production]
workers_dev = false
JWT_TOKEN = "production random string"
STRIPE_TOKEN="production random string"
Thanks for your help!
…On Sat, May 27, 2023 at 8:08 AM Steven Endres ***@***.***> wrote:
I am investigating the jwt string in dev.vars.
On Sat, May 27, 2023 at 8:06 AM Steven Endres ***@***.***> wrote:
>
> Hi Paul,
>
> I put a version on cloudflare at passkeys-demo.urstp.io for you to see
> the errors I am receiving using your demo. This site is the best way for me
> to communicate with you about the errors. I have no interest in hosting a
> demo any longer than it takes to debug the webauthn problems and will take
> it down once we have worked through the issues. I removed your logo and
> left your disclaimer in the html.
>
> Here is a screen shot of the errors I face. You should be able to
> recreate these in your own browser.
>
> [image: image.png]
>
>
>
>
> On Sat, May 13, 2023 at 9:17 AM Steven Endres ***@***.***> wrote:
>
>> I was able to get a simple version that works locally and live(custom
>> domain) last night. I followed the instructions for setting up the domain
>> and the certificate for ssl here:
>>
>> https://simplewebauthn.dev/docs/advanced/example-project
>>
>> I'll apply what I learned to your worker next.
>>
>> On Sat, May 13, 2023 at 8:59 AM Paul Haedrich ***@***.***>
>> wrote:
>>
>>> Any luck getting it working on a live Worker?
>>>
>>> —
>>> Reply to this email directly, view it on GitHub
>>> <#3 (comment)>,
>>> or unsubscribe
>>> <https://github.com/notifications/unsubscribe-auth/AAEVLYAE7DFMKGPOEJCXVSLXF6ASVANCNFSM6AAAAAAX5AIVZQ>
>>> .
>>> You are receiving this because you authored the thread.Message ID:
>>> ***@***.***>
>>>
>>
|
Hi Paul,
I was able to use the following setup to run the passkey-demo worker in
development mode. Brew install cloudflared if you don't have it. It's like
ngrok but tailored for cloudflare.
1. In one terminal run > npx wrangler dev --port 3000
2. In another terminal run > cloudflared tunnel --url http:https://localhost:3000
Cloudflared will create a tunnel and a temporary url for accessing your app
through your cloudflare zone to your local worker instance. The temporary
version of the url looks something like:
https://<some random phrase>.trycloudflare.com
With this setup, there is no need to change from https to http for local
development.
Best,
Steve
…On Sat, May 27, 2023 at 8:46 AM Steven Endres ***@***.***> wrote:
Adding the following lines to my wrangler.toml file got it to work:
[vars]
# I used a 16 char random string
JWT_TOKEN = "some simple string"
node_compat = false
# Override values for `--env staging` usage
[env.staging]
workers_dev = false
JWT_TOKEN = "staging random string"
# Override values for `--env production` usage
[env.production]
workers_dev = false
JWT_TOKEN = "production random string"
STRIPE_TOKEN="production random string"
Thanks for your help!
On Sat, May 27, 2023 at 8:08 AM Steven Endres ***@***.***> wrote:
> I am investigating the jwt string in dev.vars.
>
> On Sat, May 27, 2023 at 8:06 AM Steven Endres ***@***.***> wrote:
>
>>
>> Hi Paul,
>>
>> I put a version on cloudflare at passkeys-demo.urstp.io for you to see
>> the errors I am receiving using your demo. This site is the best way for me
>> to communicate with you about the errors. I have no interest in hosting a
>> demo any longer than it takes to debug the webauthn problems and will take
>> it down once we have worked through the issues. I removed your logo and
>> left your disclaimer in the html.
>>
>> Here is a screen shot of the errors I face. You should be able to
>> recreate these in your own browser.
>>
>> [image: image.png]
>>
>>
>>
>>
>> On Sat, May 13, 2023 at 9:17 AM Steven Endres ***@***.***>
>> wrote:
>>
>>> I was able to get a simple version that works locally and live(custom
>>> domain) last night. I followed the instructions for setting up the domain
>>> and the certificate for ssl here:
>>>
>>> https://simplewebauthn.dev/docs/advanced/example-project
>>>
>>> I'll apply what I learned to your worker next.
>>>
>>> On Sat, May 13, 2023 at 8:59 AM Paul Haedrich ***@***.***>
>>> wrote:
>>>
>>>> Any luck getting it working on a live Worker?
>>>>
>>>> —
>>>> Reply to this email directly, view it on GitHub
>>>> <#3 (comment)>,
>>>> or unsubscribe
>>>> <https://github.com/notifications/unsubscribe-auth/AAEVLYAE7DFMKGPOEJCXVSLXF6ASVANCNFSM6AAAAAAX5AIVZQ>
>>>> .
>>>> You are receiving this because you authored the thread.Message ID:
>>>> ***@***.***>
>>>>
>>>
|
@spendres Oh that's awesome! Thanks for your dedication 😊 |
This is a nice start to a demo, but the login with passkeys button either spins when deploying locally, or cannot authenticate when deployed to cloudflare with a custom domain.
I suspect that the calls to encryption need domain specific settings, but haven't researched the code yet.
The text was updated successfully, but these errors were encountered: