WebPage Opening vs. Shown challenge

[Jeannot_Muller]

@Anthony_G_Cyphers

you’re dragging this off-topic and confusing the issue when they’re trying to track down an event-related issue

Granted, sorry! - But I think that from the discussion we have the headline is just not precise enough, as from @William_Reynolds response I think he is exactly trying to solve what you and I described.

I still believe William is asking 2 related questions and it as such two-fold:

1. There is the opening vs. shown challenge in general (as it doesn’t seem to be completely logical when to use the right event. Some commands only work properly in either opening or shown)
2. It’s a bit unclear how to implement security properly. From this thread it seem we all agree that the events in a page are not an option, you must code all permissions before calling a new page / dialog. I’m fine with this approach, but it is unclear to me yet (if a page can really not accessed via any other way). I definitely derailed on that piece, again sorry and I opened a new thread.

@Anthony_G_Cyphers

That said, to be entirely safe, you should validate the user’s login before attempting to send them to any secure pages rather than sending those pages, validating the user, then having your app realize they’re not allowed to access a resource and change to a different page

@William_Reynolds

In a perfect word the default page could load, a Session is born, and moving away from that page to an unauthorized page would force a security challenge.