W
wvdgraaf
Guest
With a little help from a colleague, I changed idmstartup.p to omit the oech1:: string while reading the domains.json file and add the oech1:: string in the domains.json file. So apparently there's a small bug in this program that causes a corrupt key value in the security registration. hCP:validate-seal("oech1::1a051b2c373c"). will now be executed correctly. Also a small bug-fix in dumpCP.p. if ( p_hCP:qualified-user-id = "") OR ( p_hCP:qualified-user-id = ?) then message " ID: '" + p_hCP:qualified-user-id + "'". This will of course never give you a userid. So I changed it into if ( p_hCP:qualified-user-id <> "") AND ( p_hCP:qualified-user-id <> ?) then message " ID: '" + p_hCP:qualified-user-id + "'". Only problem is that I don't want to use a key-value in my code! So the use of the validate-seal method is not desired. I still want to use SECURITY-POLICY:SET-CLIENT(hCP). Should it be reported as a Progress Bug?
Continue reading...
Continue reading...