You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "Sachin (Jira)" <ji...@apache.org> on 2022/07/04 09:23:00 UTC

[jira] [Commented] (OFBIZ-12637) Login is forced when we return from a third party payment gateway/application

    [ https://issues.apache.org/jira/browse/OFBIZ-12637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17562098#comment-17562098 ] 

Sachin commented on OFBIZ-12637:
--------------------------------

Hi Jacques,

I tried the above by passing the said parameters, but its not working,

I made some observations as below:
1. While using ecommerce in localhost, we found when we try to pay by  PayPal, additional cookies stored in browser for PayPal while the ecommerce/ecomseo cookies still exists.

2. But when we try to pay by vivawalet, it is deleting the ecommerce/ecomseo cookie first and then creating/loading the viva wallet related cookies.  Since the cookie for ecommerce/ecomseo is deleted it is asking to login when redirected to ecommerce/ecomseo.

Is there any setting which will keep the ecommerce/ecomseo cookie alive?

Thanks in advance.

 

> Login is forced when we return from a third party payment gateway/application
> -----------------------------------------------------------------------------
>
>                 Key: OFBIZ-12637
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-12637
>             Project: OFBiz
>          Issue Type: Bug
>          Components: ecommerce
>    Affects Versions: 18.12.05
>            Reporter: Sachin
>            Priority: Minor
>
> We are trying to integrate Third Party Payment "Viva Wallet (UK)" service as part of our project.
> We used Viva Wallet successfully with Ofbiz version 16.11.07 (we could move to third party site on click of a link and finish the process and return back successfully to our application).
> While integrating with the latest Ofbiz 18.12.05, it forces a user login on return (it invalidates the existing session).
> Are we missing something in this process which is new in ver 18.12.05?
> In case this query is not clarifying the issue, please let us know we will try to revise this with more appropriate information.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)