Newsgroups: wclistserve.win.server
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.6)
for WINServer@winserver.com; Tue, 27 Nov 2018 09:01:25 -0500
Received: from [192.168.1.68] ([99.121.5.8])
by winserver.com (Wildcat! SMTP v7.0.454.6) with ESMTP
id 2324216775.1.1796; Tue, 27 Nov 2018 09:01:23 -0500
Message-ID: <5BFD4E36.5030609@winserver.com>
Date: Tue, 27 Nov 2018 09:01:26 -0500
From: Hector Santos
Organization: Santronics Software, Inc
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101
Thunderbird/24.8.1
MIME-Version: 1.0
To: WINServer@winserver.com
Subject: Re: [WINServer] WcWEB PrintLoginForms Examples
References: <5BFCB6C7.9010109@winserver.com>
In-Reply-To: <5BFCB6C7.9010109@winserver.com>
Content-Type: multipart/mixed; boundary="------------070506090806040200000103"
Wow, this worked really well and a number of you guys tried it out!! :)
Testing with my iPhone with the Sarafi browser, I found that the
printloginform-topbarcat with the top bar for login and the full
screen cat eyes in tall grass image, did not show the Select Login
form pulldown. It was in the background. So I will have to adjust
the CSS for Safari, but this will give us a start for a
PrintLoginForm-MOBILE tamplate for login purposes!!
That was the original idea behind doing all this with the then new
"WcWeb Authentication" programming system back in 2006. The idea was
not such much to get users the ability to change the login form, but
to give the sysop, operator something they can set when
installing/setting up their wildcat! system.
I am going to update the PrintLoginForm.zip, make such adjustments.
The current zip puts the PrintLoginForm-*.wct files in the
http\public\* folder. It doesn't have to be there. It can actually
be in a private folder because it is a server-side include. So that
will be part of the adjustements.
For the test at the aws2.winserver.com, in case, you want to explore
this on your end, what I did was as follows:
1) Download the printloginforms.zip from the AUP.CHM in the "Web
Authentication | Example Login Forms" section. Assuming you put the
zip into your wildcat folder, unzip it like this:
unzip -j printloginforms.zip http\public\printlogin*.* -d
http\template\custom
unzip -j printloginforms.zip http\public\graphics\* -d
http\public\graphics
The printloginform*.* files are now in your http\template\custom
folder and the graphic files in the http\public\graphics folder.
2) Create/edit the http\template\custom\LoginOptionsCustom.inc file
Create/Edit this file and for the login form you want to use, set the
Login.CustomForm variable, for example, to use the login form with the
splash image like at winserver.com, do this:
@set Login.CustomForm="wc:\http\template\printloginform-splash.wct"@
NOTE:
You might be thinking, if the printloginform-*.wcts are in the custom
folder, why not set it like this:
@set
Login.CustomForm="wc:\http\template\custom\printloginform-splash.wct"@
yes, you could do that, but because of the way wcWeb works with the
"http\template" folder, you can also set it both ways and wcWeb will
still find it. The reason is because, its possible in the future we
can have a stock printloginform-*.wct in the http\template in the
future. This was the original idea, but it was left as an option for
sysops to explore and do themselves. I think we might just do this
with a new option to change it using a LoginOptionCustom.Inc override.
3) Go to wcConfig | Web Server | Authentication Options | and set:
[X] Allow WcNavigator Web Login Challenge
[X] Allow Cookie-based Authentication
I would turn off:
[_] Allow Basic
[_] Allow Digest
The only reason to keep them all on, is when you have users who don't
use JavaScript. Well, back in 2006 when this was all done, to try to
be SMART for Browser Login Popups windows and Form-based logins, it
worked really really well, but was inconsistent when a
non-authenticated URL came in for a private authenticated resource,
like going directly to Who's online or to your inbox, etc, where
Wildcat! has to log the user in first. What happen is that users got
both Popups and Login forms. It was a chicken and egg situation, so,
to make this story short (if that is possible with me ), just pick
one or the other, html-based login forms (Cookie-based, WcNavigator)
or Browser Popups (BASIC, DIGEST).
That's it!! It should all work now.
Finally, in the LoginOptionsCustom.inc files, if you trying different
ones, you can just add another line to override the previous one:
@set Login.CustomForm="wc:\http\template\printloginform-splash.wct"@
@set Login.CustomForm="wc:\http\template\printloginform-topbarcat.wct"@
@set Login.CustomForm="wc:\http\template\printloginform-nav.wct"@
WcWeb will use the last one set.
On 11/26/2018 10:15 PM, Hector Santos wrote:
> I just created this to explore the different example prints login
> forms available on our setup:
>
> http://aws2.winserver.com
>
> You can select the "PrintLoginForm" to change the login form and it
> will stick with you (based on your IP address), so you won't affect
> anyone else.
>
> Check it out!!
>
> PrintLoginForms are described in the AUP.CHM under "Web Authentication
> | Example Login Forms"
>
> Note, this web site requires SSL, but I didn't get a cert for it. So
> just proceed with the connection.
>
>
--
Hector, Engineering & Technical Support
Santronics Software, Inc.
http://www.santronics.com (sales)
http://www.winserver.com (support)
http://www.winserver.com/AupInfo (Online AUP Help)
Office: 305-248-3204
begin:vcard
fn:Hector Santos
n:Santos;Hector
email;internet:winserver.support@winserver.com
tel;work:305-248-3204
version:2.1
end:vcard
--- Platinum Xpress/Win/WINServer v3.1
* Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
SEEN-BY: 1/123 15/0 90/1 105/7 10 11 44 81 85 500 106/201 120/340
SEEN-BY: 123/131 129/305 153/7715 218/700 226/30 227/114 229/110 111
SEEN-BY: 229/112 113 114 206 307 317 424 426 428 470 550 664 700 266/512
SEEN-BY: 282/1038 317/3 320/219 322/757 342/200 396/45 460/58 633/280
SEEN-BY: 712/848
PATH: 105/81 229/426
|
