Details

    • Type: Research
    • Status: Done
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: Integration with CBAT
    • Labels:
      None

      Description

      Embedding DMS UI into Third Site

        Attachments

        1. CBAT.html
          2 kB
        2. CBES.html
          2 kB
        3. DmsIntegration.html
          2 kB

          Issue Links

            Activity

            Hide
            rohan.khandave Rohan J Khandave (Inactive) added a comment -

            As per discussion with Samir , we are going with basic authentication and now we are working on POC for same.

            Show
            rohan.khandave Rohan J Khandave (Inactive) added a comment - As per discussion with Samir , we are going with basic authentication and now we are working on POC for same.
            Hide
            rohan.khandave Rohan J Khandave (Inactive) added a comment -

            We are working on with Basic authentication, client send user name & password along with desire page/ URL with encoding of base 64 string.
            We will authenticate that user and if user is valid return user details and return URL to navigate. So client can view page in iframe.

            Show
            rohan.khandave Rohan J Khandave (Inactive) added a comment - We are working on with Basic authentication, client send user name & password along with desire page/ URL with encoding of base 64 string. We will authenticate that user and if user is valid return user details and return URL to navigate. So client can view page in iframe.
            Hide
            rohan.khandave Rohan J Khandave (Inactive) added a comment -

            As per discussion with Samir on 01/22/2019 , we are not going to use user name & password , instead of that we are going to use UserDID & AccountDID. Also Source Product Id , Language Id.

            So user can see data only for provided account & source product [ex. CBAT]

            So we are working on these changes.

            Show
            rohan.khandave Rohan J Khandave (Inactive) added a comment - As per discussion with Samir on 01/22/2019 , we are not going to use user name & password , instead of that we are going to use UserDID & AccountDID. Also Source Product Id , Language Id. So user can see data only for provided account & source product [ex. CBAT] So we are working on these changes.
            Hide
            rohan.khandave Rohan J Khandave (Inactive) added a comment -

            This JIRA we consider for POC of embedded UI , which is done.

            We have created new JIRA DMS-640 for authentication purpose, here we use AccountDID & UserDID.

            CC – Samir , Swapnil Pandhare 

            Show
            rohan.khandave Rohan J Khandave (Inactive) added a comment - This JIRA we consider for POC of embedded UI , which is done. We have created new JIRA DMS-640 for authentication purpose, here we use AccountDID & UserDID. CC – Samir , Swapnil Pandhare  
            Hide
            Ganesh.sadawarte Ganesh Sadawarte (Inactive) added a comment -

            code review & conflict resolution.

            Show
            Ganesh.sadawarte Ganesh Sadawarte (Inactive) added a comment - code review & conflict resolution.
            Hide
            jayshree.nagpure Jayshree Nagpure (Inactive) added a comment -

            Testing on preproduction completed
            Refer attached screencapture
            CBAT.html CBES.html DmsIntegration.html

            Closing this ticket

            Priya Dhamande Swapnil Pandhare Samir Sachin Hingole

            Show
            jayshree.nagpure Jayshree Nagpure (Inactive) added a comment - Testing on preproduction completed Refer attached screencapture CBAT.html CBES.html DmsIntegration.html Closing this ticket Priya Dhamande Swapnil Pandhare Samir Sachin Hingole

              People

              Assignee:
              jayshree.nagpure Jayshree Nagpure (Inactive)
              Reporter:
              rohan.khandave Rohan J Khandave (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 40h Original Estimate - 40h
                  40h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 46h
                  46h