1 of 1 people found this helpful
Yes, you can but why do that work when it is already done for you. Simply direct the user to the WebDirect URL. If the database requires authorisation, it displays a login form
Use the homepage parameter in the URL to tell WebDirect to return the user to your wordpress site when they logout.
I want to keep it as clean as possible. I feel like a user coming to a site to then be redirected to WebDirect to then login at WebDirect will create a situation of asking, "Why did I have to go to the first site?" At the same time, going directly to WebDirect clogs things up as well.
Will definitely use homepage parameters to send to the WP site on exit!
Is there anything different needed for the php in the WordPress page that would be different from not a WordPress site?
Why did they have to visit your wordPress site? Surely it wasn't just to show them a login form for WebDirect?
I'd encourage you to let WebDirect handle the authentication. It's more secure than passing user account details from site to site, probably more robust than the form that you'll device, and possibly more coherent for the user. For instance, how does your form handle name/password errors? Once the form has posted to WebDirect the filemaker authentication module will take over. It will handle errors it's way. The user who has made a typo is no longer on your wordpress site. They are now at the webDirect site staring at a login box. You could work around this by using CWP to test the authentication, getting a result back and only then going to WebDirect. However, the advantage of WebDirect is that you don't have to get your hands dirty with code. Each time you try to hide WebDirect's native methods you loose a little bit of it's benefits.