Barry is right that validation lists are intended for this kind of usage. Maybe they are sufficient.
Your question, though, is if you can call an API from PHP.
I'm not a PHP programmer, so I don't know if PHP can call programs or not. If it can't then its usefulness would be extremely limited.
An API to verify a profile/password combination would be the Get Profile Handle (QSYGETPH) API. This is a program object, so it can be called like any other program on the system. If PHP can call programs, then it can call QSYGETPH.
More likely, PHP would call a CL program (or RPG or COBOL or C) that would call the API program. The CL program would accept profile and password as input and return a 'success/failure' indication. If successful, the CL program should then call the Release Profile Handle (QSYRLSPH) API to free up the profile token since it apparently wouldn't actually be used for anything.
See:
http://publib.boulder.ibm.
Note that you'd want to be very careful in how you transported profile/password between the client browser and the system. You don't want those going across as clear text. That's another reason to consider validation lists.
Tom
Main Topics
Browse All Topics





by: _b_hPosted on 2009-06-26 at 19:57:16ID: 24726175
I think validation list entries are the way to go. That way no user profile is required on the system, and the passwords are encrypted. ir/slkbase .nsf/ 1ac66 549a214021 88625680b0 002037e/ ae 9095106997 4234862566 f1007835e4 ?OpenDocum ent
Check out this link:
http://www-912.ibm.com/s_d
Check the infocenter on the use of validation lists, especially the QSYADVLE API.
If you need more direction, post back!
Barry