Page 1 of 1

Accessing K-Rise App via JDE

Posted: February 15th, 2022, 12:18 pm
by smackie
I would like to call a K-Rise application from within JDE using an E1Page; however when access the K-Rise page I don't want to have to enter user name and password each time. Is there a way to pass this information via the url setup in JDE?

Re: Accessing K-Rise App via JDE

Posted: February 15th, 2022, 12:57 pm
by SteveCap
How do users login to your jde? Is there any single sign one that you use that you can also then send to use to login. For the time being for security you will need to login each time. We will do some research for other solutions.

Re: Accessing K-Rise App via JDE

Posted: February 15th, 2022, 2:12 pm
by smackie
Users currently sign in to JDE with their user name and password. I was thinking that I could create one account in K-Rise that could be used by all users, that would be passed with the url since the K-Rise page is an inquiry only page and users have a specific log in to JDE.

Re: Accessing K-Rise App via JDE

Posted: February 16th, 2022, 10:23 am
by SumanPrasad
Sheryl,
What you are looking for is not a user based security but a key based security. We have a feature in progress right (Task #: 10119) which will allow you to setup a key and then assign REST API or Pages to it. Only those pages can work if they send this key in url.
Meanwhile, We have a service called GetHttpData. I will work with Steve to make this service work in MVC to give you IP address (Task #: 10133). You can then restrict this page only coming from a certain IP address. Basically you will make this page unsecured and then use GetHttpData to get IP address in the Model. If it matches certain IP addresses, you can allow to proceed it in the Model otherwise just show an error message or forward to error page.
Both task 10133,10119 are in the queue and I have asked Justin to notify you once they make it to the our PD.

Re: Accessing K-Rise App via JDE

Posted: March 4th, 2022, 1:57 pm
by JustinVanRegenmorter
Task 10133 has been resolved in RunTime Revision 869.