Search results

Have you explored configuring PASOE / Spring to use the webauthn4j-spring-security extension?

It's been broken for a while - Help window resets when focus changed to code window

As an easy example use :1 - your code returns 0256 which seems to indicate that your high and low bytes are swapped. If you add: hexPart = substring( hexPart, 3, 2 ) + substring( hexpart, 1, 2 ). after the overlay you should be ok.

Hmm... it's a bit odd. ABL decimals are supposed to support 50 digits. If I just keep multiplying by two, the decimal behaves: def var i as int. def var de as decimal format '>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>.9' initial 1. repeat: display i de exp( 2, i )...

The problem is that ABL decimals are not accurate to 128 bits, try: message exp( 2, 127 ). If you want to go down this road you will need two 64 bit integers.

I generally just use google with a site filter to search progress.com: site:docs.progress.com output clipboard Output to the clipboard.

Start (pun intended) at pasoestart, and yes you are wrong about tcman being v12 related. Note that you can filter documentation on version.

The program you run from the command line cannot have any input parameters. -param will not pass input parameters, it will set session : parameter which you can use in a wrapper: run your.p ( entry( 1, session:parameter ), entry( 2, session:parameter ) ).

Are you deploying source code? We deploy 11.7, 12.2 and 12.8 r-code, so it would be: assign cSSLProtocols[1] = 'TLSv1.2':u &if proversion >= '12.8' &then cSSLProtocols[2] = 'TLSv1.3':u &endif But I do have my doubts about the protocol order, I would want 1.3 first if it can be...

So by restricting to TLS v1.2 you are not silently hanging on TLS v1.3 and now back into "normal" error territory - see Progress Customer Community

Check ciphers and transport protocols. These can be restricted by code or by environment variables - see Progress Customer Community There have been mismatches between what sslc supports and what the ABL socket supports. TLS 1.3 being an earlier troublemaker.

1. check your propath - are you referencing 11.7 libraries 2. message search( 'OpenEdge/Logging/LoggerBuilder.r' ).

tcman is the instance specific version, it will be in your <pas-instance>/bin folder. It is copied along with the rest of the instance from <dlc>\servers\pasoe To create an instance use pasman

Eclipse Jetty is the web server used by OpenEdge Explorer in 11.7. In 12.2 it became just another PASOE instance. It's port, 9090, should not be open to everyone. As to updating Jetty... 11.7's retirement date is in April 2025 - so this may be the time to upgrade to 12.2 or 12.8.

Architectural flaws are not a detail that can be fixed by fine-tuning.

My bad, the container is running Debian/GNU Linux 8 - ProgressAblDojo which seems to be using Linux kernel 3.16 which is rather old.

No, 12.8 is not yet supported on the Linux platform that ABLDojo is running on. As per that doc a bunch of Linux flavours were added to the 12.8 supported list per May 1st, but I think ABLDojo was running on Ubuntu.

Progress ran into their desupport of the Linux version ABLdojo is running on. :-)

I cannot comment on the compatibility, but your hex encoded strings did intrigue me. You only need to escape tilde (~), opening curly brace ({) and backslash (\) to keep it legible: patternBas = string( hex-decode(...

If you add [ code ] [ /code ] tags around your code you make it readable by not losing indentation and as an added bonus you get no emoji nonsense. /* progressb1 */ /* */ THIS-OBJECT:progressb1:BackColor = System.Drawing.SystemColors:Control. THIS-OBJECT:progressb1:ForeColor =...