Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
16
Web Server - Ask For Help / Re: Possible NT14 settings bug (ACME challenge type setting)
« on: September 10, 2023, 12:32:19 PM »
Thanks! 
17
Web Server - Ask For Help / IP V6 bit me
« on: September 08, 2023, 03:23:42 PM »
This is, admittedly, an edge case that most people will probably not encounter. But worth awareness...
Aside - Bruce, the NetWebClient in NetDemo has an IPV6 checkbox but it doesn't do anything. For my testing I replaced it with radio buttons for Net:IPvAuto, Net:IPv4, Net:IPv6
I would suggest you modify the NetDemo app that way... it's useful for testing.
/Aside
I have various apps running on a Windows 2019 server in an Active Directory domain that is set up with only IPv4 DNS.
The two apps involved in this problem are both ones I'm in the process of converting from NT12 to NT14. One is an API server, the other has an API client.
After rebuilding, I set the server to serve IPv4.
I did not change the client.
Its default behavior (Net:IPvAuto) did not work for me.
I guess that whatever is happening takes place inside the NetTalk DLL, so I'm not sure how you're doing the auto.
Your docs say: "By default, and if Family is set to Net:IPvAuto or Net:IPv4 then an IPv4 DNS Lookup will happen on this name first".
But what shot me in the foot (I did not shoot MYSELF in the foot!!) is apparently how Windows handles a lookup when it "knows" that the server in question is itself.
As you can see from the first pic, doing an NSLOOKUP (which uses the DNS server) resolves to an IPv4 address (which is all that our DNS handles).
But doing a PING of the same FULLY-QUALIFIED DNS ADDRESS returns a loopback IPv6 address.
I don't know if that is the cause... but the net client compiled without specifying IP family refuses to connect to my API server. If you were actually doing a DNS lookup I would have thought that "auto" would have figured out to use IPv4. If you're doing a PING internally, it would have found the IPv6.
If I force the client to use IPv4, all is well in the world. So at least in my edge case, "auto" is not bullet-proof.
More grey hairs... sigh...
Cheers,
Jane
Aside - Bruce, the NetWebClient in NetDemo has an IPV6 checkbox but it doesn't do anything. For my testing I replaced it with radio buttons for Net:IPvAuto, Net:IPv4, Net:IPv6
I would suggest you modify the NetDemo app that way... it's useful for testing.
/Aside
I have various apps running on a Windows 2019 server in an Active Directory domain that is set up with only IPv4 DNS.
The two apps involved in this problem are both ones I'm in the process of converting from NT12 to NT14. One is an API server, the other has an API client.
After rebuilding, I set the server to serve IPv4.
I did not change the client.
Its default behavior (Net:IPvAuto) did not work for me.
I guess that whatever is happening takes place inside the NetTalk DLL, so I'm not sure how you're doing the auto.
Your docs say: "By default, and if Family is set to Net:IPvAuto or Net:IPv4 then an IPv4 DNS Lookup will happen on this name first".
But what shot me in the foot (I did not shoot MYSELF in the foot!!) is apparently how Windows handles a lookup when it "knows" that the server in question is itself.
As you can see from the first pic, doing an NSLOOKUP (which uses the DNS server) resolves to an IPv4 address (which is all that our DNS handles).
But doing a PING of the same FULLY-QUALIFIED DNS ADDRESS returns a loopback IPv6 address.
I don't know if that is the cause... but the net client compiled without specifying IP family refuses to connect to my API server. If you were actually doing a DNS lookup I would have thought that "auto" would have figured out to use IPv4. If you're doing a PING internally, it would have found the IPv6.
If I force the client to use IPv4, all is well in the world. So at least in my edge case, "auto" is not bullet-proof.
More grey hairs... sigh...
Cheers,
Jane
18
Web Server - Ask For Help / Re: Possible NT14 settings bug (ACME challenge type setting)
« on: September 08, 2023, 02:59:32 PM »
Changing the declaration to a LONG on line 825 of netweba.tpw seems to give the behavior I was expecting.
19
Web Server - Ask For Help / Possible NT14 settings bug (ACME challenge type setting)
« on: September 06, 2023, 02:41:00 PM »
Bruce,
Converting my first app to NT14 from 12.63. Thanks for the walk-through on ClarionLive.
I set Challenge Method to Manual (hoping that's a handy new setting for not using Let's Encrypt for a website that has a manual cert.)
The radio button sets the value to -1
set:AcmeChallenge is a byte.
The serverSettings XML translates that -1 to 255.
Is this the intended behavior? Should set:AcmeChallenge be a LONG? (Since net:manual is declared as equate(-1) in NetAcme.inc I don't think it should be a BYTE).
Cheers,
Jane
Converting my first app to NT14 from 12.63. Thanks for the walk-through on ClarionLive.
I set Challenge Method to Manual (hoping that's a handy new setting for not using Let's Encrypt for a website that has a manual cert.)
The radio button sets the value to -1
set:AcmeChallenge is a byte.
The serverSettings XML translates that -1 to 255.
Is this the intended behavior? Should set:AcmeChallenge be a LONG? (Since net:manual is declared as equate(-1) in NetAcme.inc I don't think it should be a BYTE).
Cheers,
Jane
20
Web Server - Ask For Help / Re: RUnning 2 web apps on 2 different ports - Warning <Display Name> could not load
« on: September 06, 2023, 02:31:16 PM »
Are you using Self Service?
21
Web Server - Ask For Help / Re: JavaScripts problem
« on: September 06, 2023, 08:02:33 AM »
Probably The Old "web folder isn't where I think it is" Trick.
If you copied the myappname.ServerSettings.xml file from your development machine you've hard-copied folder settings from that machine.
Either delete that XML file and let NetTalk recreate it or else edit the path in the settings on your web server window while it's running.
If you copied the myappname.ServerSettings.xml file from your development machine you've hard-copied folder settings from that machine.
Either delete that XML file and let NetTalk recreate it or else edit the path in the settings on your web server window while it's running.
22
Web Server - Ask For Help / Re: NT 14 Floating Labels
« on: August 24, 2023, 09:17:24 AM »
To be more specific, line 3166 in netweba.tpw whence that line is written into gzipall.bat
23
Web Server - Ask For Help / Re: NT 14 Floating Labels
« on: August 24, 2023, 08:50:04 AM »
There's a typo in gzipall.bat
It reads (in multiple places - once for each theme):
should be:
It reads (in multiple places - once for each theme):
Code: [Select]
IF EXIST web\styles\nt-labels.css type web\styles\netweb.css >> web\themes\base\theme.fat.cssshould be:
Code: [Select]
IF EXIST web\styles\nt-labels.css type web\styles\nt-labels.css >> web\themes\base\theme.fat.css24
Web Server - Ask For Help / Re: WebServer Single Sign On (SSO)
« on: August 23, 2023, 01:35:51 PM »
Single sign-on with Azure AD is what we aim for .
Even then, what does that mean?
1. The user logs in to your app using username/password that's stored in Azure AD and app authenticates those credentials against AD?
2. The app somehow magically knows the user's credentials and logs him in without any additional login steps (like a saved OAUTH token) ?
3. The app sends an NTLM challenge to the browser to authenticate the user (the way Sharepoint and SSRS can do internally)?
4. Integrated Windows authentication (which is probably the same as #3)?
Another Azure-specific link for #4: https://learn.microsoft.com/en-us/aspnet/visual-studio/overview/2012/windows-azure-authentication
25
Web Server - Ask For Help / Re: NT 14.01 compile error
« on: August 17, 2023, 05:56:17 PM »
Reflection 1.24 - from the history:
"Add: Field type: rf:interface"
"Add: Field type: rf:interface"
26
Web Server - Ask For Help / Re: Themer compile errors
« on: August 12, 2023, 06:33:46 PM »
Is that error message related to a service method?
From the version history:
From the version history:
Quote
12.48 - 9 November 2022
IMPORTANT : If using xFiles for ServiceMethods, requires xFiles 4.05 (or later).
27
Web Server - Ask For Help / Re: Internal error with server
« on: July 24, 2023, 05:07:27 PM »is it maybe possible that any library, whether it's NT or any other with Clarion, may cause the message to pop up, event after setting system{PROP:MessageHook} = address (MyMessage)?
Thanks
Yes!
If you're using SQL, the SQL driver can pop up a login message box no matter what you have hooked in Clarion.
To suppress that you can use the driver option
/LOGONSCREEN=FALSE
I use that switch in conjunction with the SQL disconnect class that Rick Martin showed as part of CIDC 2020 (and Capesoft MessageBox).
28
Web Server - Ask For Help / Re: Attacked by Let's Encrypt
« on: July 20, 2023, 11:36:58 AM »
What? Me? FUD?? Pshaw!
In fairness, my hyperbolic clickbait post headline was followed up by a more specific reference to ACME rather than to Let's Encrypt itself
Clearing the CA field seems to have inhibited its compulsion to "help" me with a new certificate.
It's running as a service so I can't see whether it put anything in the log about doing a certificate check.
Good to know about the equate in the inc file but I don't want to rebuild the app just to change that unless I have to.
Anyway, people not using Let's Encrypt might want to be aware of this possibility.
With all due respect to Let's Encrypt, which I'm hoping to use with the new ACME magic promised for NT 14.
FUDD?
In fairness, my hyperbolic clickbait post headline was followed up by a more specific reference to ACME rather than to Let's Encrypt itself
Clearing the CA field seems to have inhibited its compulsion to "help" me with a new certificate.
It's running as a service so I can't see whether it put anything in the log about doing a certificate check.
Good to know about the equate in the inc file but I don't want to rebuild the app just to change that unless I have to.
Anyway, people not using Let's Encrypt might want to be aware of this possibility.
With all due respect to Let's Encrypt, which I'm hoping to use with the new ACME magic promised for NT 14.
FUDD?
29
Web Server - Ask For Help / Re: Confirm Form Resubmission - minimize?
« on: July 19, 2023, 06:47:59 PM »
Google search for
You'll see a number of possible workarounds, none of which are elegant.
Jane
Code: [Select]
chrome what triggers form resubmission messageYou'll see a number of possible workarounds, none of which are elegant.
Jane
30
Web Server - Ask For Help / Re: Attacked by Let's Encrypt
« on: July 19, 2023, 06:44:14 PM »
I had had the word "something" in the CA Account entry field on the web server.
I've blanked that field to see whether that will inhibit the automatic cert-fetching.
I've blanked that field to see whether that will inhibit the automatic cert-fetching.