routine-level on error undo, throw.
using System.Security.Cryptography.X509Certificates.*.
using System.Security.Cryptography.*.
using System.Security.Permissions.*.
class auth.ClientCertificate final inherits AoSBase:
&scoped-define sub-system 'CLNT_CERT'
&scoped-define...
The auth.ClientCertificate is a class which I developed to wrap the logic which fetches the SSL certificate from the Windows certificate store. I did not include it. Do you need a sample on how to get the certificate from the Windows certificate store?
Ooops, forgot
using System.*.
using System.Text.*.
using System.IO.*.
using System.Net.*.
using System.Security.Cryptography.X509Certificates.*.
using System.Security.Cryptography.*.
The ABl (at least with OE 11.6) does not support the SSL client certificate except for WebService calls. With standard HTTPS get and post requests you cannot use it. Here @ my employer we all login to our Windows 7 systems with a smartcard. During login to Windows the SSL client certificate...
Since the ABL does not support the SSL client certificate I use the .NET HttpWebRequest object. Obviously our client is running on Windoze.
On Solaris we use wget.
Please don't get me wrong, but, doing security right is not an easy task and probably never will be. That's maybe also why we read so much about security flaws and so many software fails to implement security correct or does not implement security at all. There always will be a tradeoff between...
Have a look at this KB article which basically explains how to set up SQL92 security
Progress KB - Basic Guide to Defining Progress SQL-92 Database Permissions & Security
That you can only find in the documentation of the 3rd party com object. In the case of Excel, Word and other MS Office stuff Google is your best friend. A search for "excel com interface" comes up with a lot of stuff that might help you.
The com object viewer from Progress is just a first start...
On a hunch:
When you reference classes in procedures which interface has changed - depending on the order which they are compiled you might hit that error. I know this shouldn't happen because every class referenced in another class or procedure should be compiled up front, but my experience...
As far as I know you can't directly cast a .NET array to ABL extents. You need to capture the output as .NET System.Array, iterate over the array and cast each individual member to what you expect.
define variable currentDomain as System.AppDomain no-undo.
define variable...
As per my experience - YMMV - mostly replace the dot '.' with colon ':'.
Sometimes - when the output of the .NET object is an Array I use the .NET Array object and iterate through the array casting to the particular object type.
Heavy Regards, RealHeavyDude.
That's a behavior on Windows which I don't like: Everybody's need to put everything into the Windows PATH. If you display the PATH variable on a typical Windows system you will find all kinds of crap on it. This is, where I think, Progress is superior with the PROPATH ...
As far as I know, all assemblies you want to use in a .NET or ABL for .NET project must be installed in the Windows assembly cache. The assembly cache is usually located C:\Windows\assembly. From what I know the installation of the 3rd part product should install it there.
Plus, you need to add...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.