Auth is not fleshed out yet

I understand that, but how is it working or supposed to work?

in the demo: it’s barely working…don’t expect it to be “right”.

at the moment making any kind of auth decision is still mainly your task.

Now in terms of how it is supposed to work: well, I can give you some basics: 1. Say you want to go to Report A, which queries for attributes x, y, and z. 2. The system should scan x, y, and z (the attribute definitions, which would contain auth lambdas or something) and ask the auth machine: “Does it make sense to allow this, and if not, can you ask the user for creds to make it ok?” 3. The auth machine would go about its work (full-stack, async, possibly with auth redirects that require saving state in brower local state), and eventually sends an event back to the router (or report SM…not sure): Yes or No.

so the basic idea is still attribute-centric, possibly with additional keys you could put on target component, that interacts with a pluggable auth state machine to both acquire authorization and authentication in order to see if a route “is legal at this time”

That same plugin would likely be responsible for UI interactions.

There’s also the problem of partial approval: the route is “ok”, but some of the attributes will need to be hidden or read only…

So, its a large task. Consider the auth in the demo to be a very very bare bones starting point, and not remotely close to the real solution.

And that real solution is currently beyond my real personal needs. I’m using the reports and forms to good effect in production. I don’t need the auth system.

and many apps can do with just a “block unless auth’d” approach like in the demo, with just a bit of code wrapping the routing for auth redirect.

So, short answer: Write your own landing page. Write your own auth. Record the target URL on start (where they wanted to go, and start RAD after they are logged in (at which point you can also update the URL to trigger a bookmark nav).

Do you not want to do the lambda style for that ident i.e. a function?

Ok. I have a thread to pull on. http://book.fulcrologic.com/#NetworkInteractionsandForms Looking at the database in fulcro inspector for that example I see that the ::config is different than mine. The value at form-config-path for me is a map while the value at form-config-path in that example is an ident. Both my code and that example have similar-looking queries. [::some-attr ,,, fs/form-config-join]. But that example has an ident that matches the "model". The example uses :person/id as an ident. I'm using an ident that's different from my "user" model table. I'm using [::form ::user/id] rather than ::user/id (or equilvalently [::user/id ::user/id]. I also see the example calls fs/add-form-config* inside the mutation that initializes an "empty" new person object. I'll need to look into what that does.

(defmutation edit-new-person [_]
  (action [{:keys [state]}]
    (let [person-id    (tempid/tempid)
          person-ident [:person/id person-id]
          phone-id     (tempid/tempid)]
      (swap! state
        (fn [s] (-> s
                  (add-person* person-id "" 0)
                  (add-phone* phone-id person-id :home "")
                  (assoc :root/person person-ident)         ; join it into the UI as the person to edit
                  (fs/add-form-config* PersonForm [:person/id person-id])))))))

@U0D5RN0S1 Ah. Sorry. Yes. Same result though. The path to form-config-path still points to a value that is a map, not an ident.

do you have the initial state of the form in the component?

when i've seen this in the past it was either not adding the form config or not joining the component properly:

Make sure you have joined your form to the parent component.

{:query [:my-thing/form]}
;; should be
{:query [{:my-thing/form (comp/get-query MyForm)}]}

I’ve got the same issue =)… Will look over your code later and see if we have any similarities…