The dev experience is so bad. I’ve been testing bunch of auth as a service, this is the worst experience I’ve had so far. I previously used Auth0 at Knock (but we were paying quite a bit), so was looking for alternatives. The documentation and code base samples are often out of date, and inconsistent.

Hey @faint-judge-29851 I'm sorry to hear that you're having a difficult time with Ory. Ory is designed to be highly customizable and flexible, which can sometimes make it more complex to set up and use. The Ory team is constantly working on improving the documentation and the overall developer experience. If you find any inconsistencies or outdated information in the documentation, please let me know or if you are up to it open an issue on github.com/ory/docs so we can improve. Thanks ✌️

Its’ just all over the place. I’m just looking at simplest examples, and often it’s like Network config is mixed with self hosted. If you want to make money as a product, I think you may have to build 2 versions of the docs and examples. And focus on guided experience for paid users

What are you trying to do (framework etc) and where are you getting stuck?

I’m in the evaluation phase - trying to go through all the methods in the

class FrontendApi

and understand how each works, how different flows work for custom UI (including errors). And which flow can be initiated server side (node/python/go, something with base http minimal server), which need to be from the browser side (or mobile). All the examples (and the even the client library has just so many abstraction framework layers, and admin side functionality built in too). So it’s like peeling an onion. I like your base Golang codebase, hence giving Ory a shot. Can’t get a simple clean example with using Oy proxy and Ory network as a user.

const r = await ory.createBrowserLoginFlow({
  cookie: request.headers.cookie,
});

Does this need to be server side or client side (and why). When I use this it just gives me below data, now what am I suppose to do with this?

{
  "data": {
    "url": "/self-service/login/browser"
  },
  "headers": {
    "content-type": "application/json; charset=utf-8",
    "date": "Sat, 23 Mar 2024 15:00:13 GMT",
    "strict-transport-security": "max-age=0;",
    "vary": "Origin",
    "content-length": "37"
  }
}

I am really fighting with this also. I had really high hopes but it seems like everything thing I try from the examples doesn't work. I have an open topic right now in two different threads with no responses. I am trying to just get the simple expressjs app to work from the code-examples and it gets into an infinite redirect loop. Really frustrating.

@best-hair-72217 which examples specifically?

I think I understand now. I’ll send you my writeup in a day or so. Testing with simple node Fastify with templating. • I just got funded last month, so only have backend team. FE tech is still TBD. I’ll most likely pick either NextJs or Sveltekit. • For backend Traefik on VPC edge -> verify seshion (Ory network endpoint for forward auth) -> internal services in Node & Go • For certain routes no forward auth middleware Question: For Traefik -> forward auth via Ory Netwok, do I need caching?

@high-optician-2097 I don't want to hijack @faint-judge-29851 thread so I tagged you on the post describing my issue. I really, really want this to work for our solution so any help would be appreciated.

When I do a form POST on `http://localhost:4000/ui/login?flow=190b752d-605e-4436-a50e-fc57e9b18a77`(localhost:4000 is tunneling to Ory Network). On form error, Ory API responds with 303 with location

Location: <http://localhost:4000/ui/login?flow=190b752d-605e-4436-a50e-fc57e9b18a77>

Which will result in browser client going to Orys UI not mine. How do I fix this?