There is confusion in most of the people about what scope of a service needs to be selected while configuring any service.
Also how the term “scope” is related to a service.
5 Likes
In vConnect while configuring a service in VAHANA there are three scopes that we can define for a service.
- Device Level Session
- User Level Session
- Without Session
a. Device Level Session :-
We can configure this scope of a service, if we need to call a service before login process.
In this scope device level session is created between the front-end device and middleware.
If we need to show any information on device which is not user specific , then we can configure service session as Device level
Services like PWSYNCCONFIG , PROPERTYMASTER are kept as device level session.
b. User Level Session:-
User level session is created after the authentication process, i.e after successfully calling of AUTH service. This is why all the services which are called after login process, need to have user level session.
Services like SPTBGETLOGINDETAILS, PAN integration or any service having user specific data or services which are called after AUTH are configured as user session scope
c. Without Session :-
For scenarios where we need to configure service scope as without session mentioned as follows:-
- If we need to perform load testing for a service
- If there is no major security concerns
- If we need to call service as a Rest/Soap API by using python or java
6 Likes
In Addition to above explanation, You can refer the documentation below:
https://academy.vahanacloud.com/integration/service-management-with-vconnect/
4 Likes
What will happen if we call DEVICE_LEVEL service after AUTH i.e. after login?
Will it work or not?
5 Likes
It will work for sure, As the Device level session is the very basic session which is required and above that is User level session. You can say that User level session supports all type of sessions, but Device level session doesn’t support User level session API’s.
4 Likes