When you are using the bootstrap login, everything is on the same page and it works fine. However, if you are using your own login page instead of the bootstrap, things get a little complicated.

For starters, once you move past the login page, the protected pages you are visiting don't have any code for the security provider executor, so it's not possible to assign a text or image link to a logout behavior. When you try and use control security provider executor on one of the protected pages, you get this message:

"You need to define a DMXzone Security Provider Executor first, before you can control it."

The thing is, you can't add a security provider executor because the inside pages protected by the login don't have a login form - and they don't need one either since the custom login page was already used to get to the "inside page" where you run into this problem.

The other thing I noticed is that there's no obvious way to tie into the user account that is currently logged in. For instance, with DW server behaviors, you know that the session variable for the user is held in MM_Username, so it can be used to query the database for other user info, etc. I don't see how this is possible with DMXzone Security Provider when you're using your own custom login pages and protecting pages with the enforcer.

Can you provide any instructions, tips, or links to tutorials that address these concerns in a setup where customer login forms are used? Any help would be greatly appreciated.

Hi Steve,
You should first add the security provider executor on the page you want to use the logout behavior on by just selecting Site > DMXzone Security Proivder > Manage DMXzone Security Provider Executor > OK BUTTON
This adds the security provider on your page. Now you can add the logout behavior...
More - you can Fetch User Details by User Identity
So - the support is not poor, you just have to look at the tutorials.

Thanks for the link to the tutorial. I did look through those before writing, but obviously I missed it.

Since I'm using my own login forms, it is very confusing that you have to add the security executor using the default (bootstrap modal) option. This is what was throwing me off. Since I'm not using bootstrap modal for login, it would never have occurred to me to do that.

Thanks Teodor. Really appreciate the fast support.