Hi Rich. I verified on my 2016.2.0 instance that Delegated Authentication works for SOAP requests. Initially I had problems similar to yours. Check the following:
1. ZAUTHENTICATE.mac is in the %SYS namespace.
2. It has a line similar to
set Properties("Roles")="%Developer"
Otherwise you’ll get <PROTECT> errors.
Also, you may wish to check Devchange STC2188 – apparently Caché versions prior to 2014.1 had a problem with SOAP delegated authentication.
Excellent. It reminded me of the Translate example from my REXX programmer days, which I slightly reworked for Caché:
This example shows how to use the $TRANSLATE function to reorder the characters in a string. In the example, the last character of any four-character string specified as the third argument would be moved to the beginning of the string:
How about 'novice'? I suppose any term has its associations (good and bad) - maybe I'm thinking back to my chess playing days, but 'novice' has a nice ring for me.
go to post
Hi Rich. I verified on my 2016.2.0 instance that Delegated Authentication works for SOAP requests. Initially I had problems similar to yours. Check the following:
1. ZAUTHENTICATE.mac is in the %SYS namespace.
2. It has a line similar to
set Properties("Roles")="%Developer"
Otherwise you’ll get <PROTECT> errors.
Also, you may wish to check Devchange STC2188 – apparently Caché versions prior to 2014.1 had a problem with SOAP delegated authentication.
HTH,
Jonathan
go to post
Excellent. It reminded me of the Translate example from my REXX programmer days, which I slightly reworked for Caché:
This example shows how to use the $TRANSLATE function to reorder the characters in a string. In the example, the last character of any four-character string specified as the third argument would be moved to the beginning of the string:
go to post
How about 'novice'? I suppose any term has its associations (good and bad) - maybe I'm thinking back to my chess playing days, but 'novice' has a nice ring for me.