Hello, this is an aux Trace of a Basic Auth Request in cics
XS 0601 XSPW ENTRY - FUNCTION(INQUIRE_PASSWORD_DATA) USERID_LENGTH(8) USERID(xxxxxxxx) PASSWORD(00000000 , 00000000)
XS FE01 XSSB ENTRY FUNCTION(INQUIRE_PASSWORD_DATA) USERID_LENGTH(8) USERID(xxxxxxxx) PASSWORD(00000000 , 00000000) METHOD(EXTRACT)
XS FE02 XSSB EXIT FUNCTION(INQUIRE_PASSWORD_DATA) RESPONSE(OK) SAF_RESPONSE(0) SAF_REASON(0) ESM_RESPONSE(0) ESM_REASON(0)
METHOD_USED(FULL)
XS 0602 XSPW EXIT - FUNCTION(INQUIRE_PASSWORD_DATA) RESPONSE(OK)
WB 0414 WBRQ EVENT - CALL_TO_ANALYZER
....
So it seems Extract does not work and cics tries the full method. Is this the correct interpretation of trace? If yes, should extract work? I have activated all tss performance options available.
Manual
CICS attempts to verify a password using a RACROUTE
REQUEST=EXTRACT request to the external security manager. If the password
cannot be verified using this method, CICS uses a RACROUTE
REQUEST=VERIFYX call. Before CICS Transaction Server for z/OS, Version 3
Release 1, CICS always used the RACROUTE REQUEST=VERIFYX call, which is
more expensive.
...
CICS uses password verification for improved performance in the following login processes:
HTTP basic authentication with CICS web support