Routine name for user authentication !!!

[Wasim]

Hello all,

Please can anyone help me to find the "name of the routine" that EDIS uses to check and verify the user Access and verify code "user authentication", because I got confused between the XUS kernel routines that usually use to check/verify the user A/V codes.

What we found that the EDIS send an the "Proxy user credentials" then it submit the EDIS user , but I couldn't trance and find where is the RPC and the routine name that EDIS uses to receive the EDIS user credentials!!!

Thanks in advance,

[Nancy Anthracite]

Did you try looking at the XWB log for the RPC and then tracing the code from that? I think it will work with VistALink, but I am not sure it will.

 

--

Nancy Anthracite

[Wasim]

hello Nancy,
thanks for your quick answer,
Yes I looked and monitored it XWB log but i found that it calls an RPC "XUS KAAJEE GET USER INFO" where I couldn't find the exact routine that i'm looking for it.
this RPC calls a routine that checks on the proxy user's credintails not on the normal edis user's credintals!!! so i think there is something weird in the design and i can't understand and trace it.

simply , i'm just looking for the name of the routine that checks the EDIS user credentials.

[Nancy Anthracite]

KAAJEE I don't know about. But I bet David does. Let's see if we can get his attention. He is on vacation.

 

--

Nancy Anthracite

 

On Tuesday, December 29, 2015 07:49:11 AM Wasim wrote:

> hello Nancy,

> thanks for your quick answer,

> Yes I looked and monitored it XWB log but i found that it calls an RPC "XUS

> KAAJEE GET USER INFO" where I couldn't find the exact routine that i'm

> looking for it.

> this RPC calls a routine that checks on the proxy user's credintails not on

> the normal edis user's credintals!!! so i think there is something weird in

> the design and i can't understand and trace it.

>

> simply , i'm just looking for the name of the routine that checks the EDIS

> user credentials.

>

> On Tuesday, December 29, 2015 at 4:23:21 PM UTC+2, Nancy Anthracite wrote:

> > Did you try looking at the XWB log for the RPC and then tracing the code

> > from that? I think it will work with VistALink, but I am not sure it will.

> >

> >

> >

> >

> > Nancy Anthracite

[Nancy Anthracite]

Does this help?

 

OUTPUT FROM WHAT FILE: REMOTE PROCEDURE//

Select REMOTE PROCEDURE NAME: XUS KAAJEE GET USER INFO

ANOTHER ONE:

STANDARD CAPTIONED OUTPUT? Yes// (Yes)

Include COMPUTED fields: (N/Y/R/B): NO// BOTH Computed Fields and Record Number

(IEN)

 

NUMBER: 2164 NAME: XUS KAAJEE GET USER INFO

TAG: USERINFO ROUTINE: XUSKAAJ

RETURN VALUE TYPE: ARRAY

DESCRIPTION:

Returns a variety of information needed for the KAAJEE logon.

INPUT PARAMETER: CLIENT-IP PARAMETER TYPE: LITERAL

REQUIRED: YES SEQUENCE NUMBER: 1

DESCRIPTION:

IP address of the client workstation, used for logging (signon log)

and IP blocking (failed access attempts).

INPUT PARAMETER: SERVER-NM PARAMETER TYPE: LITERAL

REQUIRED: YES SEQUENCE NUMBER: 2

DESCRIPTION:

Identifying name for the calling application or server,

used for logging (signon log).

RETURN PARAMETER DESCRIPTION:

OUTPUT:

Result(0) is the users DUZ.

Result(1) is the user name from the .01 field.

Result(2) is the users full name from the name standard file.

Result(3) is the FAMILY (LAST) NAME

 

 

--

Nancy Anthracite

 

On Tuesday, December 29, 2015 10:53:27 AM Nancy Anthracite wrote:

> KAAJEE I don't know about. But I bet David does. Let's see if we can get

> his attention. He is on vacation.

>

> > hello Nancy,

[Wasim]

OK, anyway I'm working on this with the team in Jordan, and in case we find the answer before anyone else I will reply to this post.
thank you again Nancy...

[Wasim]

We got it :)
as I guessed EDIS use it's own A/V check-up routine inside the VistALink, they don't use the usual VistA Kernal XUS routines.
the name of the routine that I was looking for is "XOBSRAKJ    ;kc/oak - VistALink Reauthentication Code,"

THANK you Nancy...

[Nancy Anthracite]

Congratulations! It does not sound like I helped at all. :-) Are you taking a look at the next version of EDIS now?

 

--

Nancy Anthracite

 

On Wednesday, December 30, 2015 01:17:13 AM Wasim wrote:

> We got it :)

> as I guessed EDIS use it's own A/V check-up routine inside the VistALink,

> they don't use the usual VistA Kernal XUS routines.

> the name of the routine that I was looking for is "*XOBSRAKJ* ;kc/oak -

> > Nancy Anthracite

[Wasim]

at least you have a quick answering and mindful ;)
About EDIS next version we didn't look to it yet, but we set it as a one of projects in the 2016's plan.