Sign in web page error
When I click on Sign in on a community page I get this error.
{"message":"invalid json response body at https://app-co-myaccountspaclientbff-we-live.azurewebsites.net/api/v1/Sso/GetZendeskSsoUrl?redirectUrl=https%3A%2F%2Fsupport.captureone.com%2Fhc%2Fen-us%2Fcommunity%2Fposts%2F4410956799761-URL reason: Unexpected end of JSON input"}
Signing in from the main page works fine.
-
Rivanni,
It seems to be necessary to have an active sign-in on the main account page before the Community sign-in works.
On the plus side, if signed in to the main account clicking the sign-in on the Community page should not require you to go through the email/password entry process another time. It should just sign you in.
The main sign-in seems to time out after some hours. The community sign-in seems to time out after a shorter period.
It has been like that for a while so I doubt it will change but you could use the "Submit a request" feature to create a Support Case if you would like an official Capture One response.
0 -
When I land on a community page through a web search, it's very inconvenient to open the main page, log in to the main account and then go back to the community page and refresh it.
When a sign in option is offered on a community page I expect it to work. Else remove this option.
Time-outs are irrelevant for a sign in to work properly.
0 -
Make a shortcut in your browser and solve the immediate frustration.
That's how I work (more or less). One gets used to it. It is not uncommon to have to sign on (often via a re-direction) to another "secure" site before being allowed to access a sub-site.
0 -
Shortcuts to all my future Google search results? Right.
BTW I use Google because it's better than the search engine of the community and as a bonus it points me to other resources as well.
It's not relevant if other sites have the same problem. If so, it should be fixed there as well.
"Get used to it." Is that how Capture One handles bugs? Something to consider before buying the program.
0
Post is closed for comments.
Comments
4 comments