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

Can't complete setup #79

Closed
ctolkien opened this Issue Mar 7, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@ctolkien
Copy link

ctolkien commented Mar 7, 2017

When trying to complete the /admin/setup step, there is an error raised (via JS):

The anti-forgery token could not be decrypted. If this application is hosted by a Web Farm or cluster, ensure that all machines are running the same version of ASP.NET Web Pages and that the configuration specifies explicit encryption and validation keys. AutoGenerate cannot be used in a cluster."

I've configured the machine key as instructed in the setup guide. I can also see X-XSRF-Token: is being passed along in the headers .

@HeyJoel

This comment has been minimized.

Copy link
Member

HeyJoel commented Mar 7, 2017

I've had an issue like this before which was caused by an additional value being added to the X-XSRF-Token header. I resolved it by disabling some of my chrome extensions but having done that I couldn't replicate the error again by turning them back on so I'm not sure if that was actually the cause or just a red-herring.

Anyway, we use the .Net AntiForgery library to create and validate the tokens but for WebApi endpoints we have to do a bit of custom formatting of the token. Your token should look a bit like this:

otYgl7rDQk5MBnoOfhO4PrYqKpKM4tN-NNNT8wt9a5uuu5DuQzL6jzOsomKjktbJZGp1AFc958-appof3p2FjxmMfdE1:ah5zQ3EpgR_RaQHZtqQWE7dSpj2v1ORNsFsW_xlavbTeubSTgfvA_1tgQxhTyvBR2WFckCIlyMbYA4rkKc0GhPHjdhE1

Note the colon delimiter between the two parts of the token. When I ran into the issue the header had an extra value added to the end separated by a comma. Is that what you are seeing?

I can't actually replicate the issue, but I've fixed it base on the assumption of a comma delimiter. You can get the fix in version 0.1.2-ci0004 in our pre-release myget feed or if you want to wait I'm hoping to get proper release in before the end of the week to fix this and a few other bugs.

@HeyJoel HeyJoel added the bug label Mar 7, 2017

@HeyJoel HeyJoel self-assigned this Mar 7, 2017

@HeyJoel HeyJoel modified the milestones: 0.1.2 Post Preview Fixes, 0.1.3 Mar 7, 2017

@HeyJoel

This comment has been minimized.

Copy link
Member

HeyJoel commented Mar 27, 2017

This change has been released in 0.1.3. I'm closing for now, but if anyone has further problems let me know and i'll re-open.

@HeyJoel HeyJoel closed this Mar 27, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment