Please remind me, is this really the case?
using system.perspective.navigate(), it does not trigger page startup script??
Please remind me, is this really the case?
using system.perspective.navigate(), it does not trigger page startup script??
Not in a single tab. Try opening a new tab.
(A "page" life cycle is not tied to a particular URL, but to the unique browser environment it opens within.)
Yes, on same tab, is what i meant..
I have existing implementation on page startup that check if user have access on page then redirect. But has a loop hole, when he has access on other page and navigate to desired page.
I wonder where you should add page DB-based authorization?
Thanks.
You should be using native view permissions, so that we enforce invariants for you:
But this not scalable, reason why existing implementation went away from this.
in other words, site admin does not equal to a developer. and has no access to designer.
If you are going to roll your own authentication, you are responsible for every corner case. Consider creating a true Identity Provider (SAML implementation) outside of Ignition, and set your project(s) to use it.
Not authentication or login to project, but protecting page resources. Just thinking out loud if there was a one place to put the DB-based page authorization script.
If really insist, put on startUp script of each view, idk.
i guess, like you said this is a guard rail not a cage.
Nothing says you have to use the same IdP for the Ignition gateway that you do for your individual Perspective projects.