Uploaded image for project: 'IGB'
  1. IGB
  2. IGBF-2549

Fix dev environment login

        Details

        • Type: Bug
        • Status: Closed (View Workflow)
        • Priority: Major
        • Resolution: Done
        • Affects Version/s: None
        • Fix Version/s: None
        • Labels:
          None

          Description

          Situation: BioViz Connect settings.ini has a variable IS_DEV_ENVIRONMENT that can be set to true/false for development/production. If set to true and a valid CyVerse username and password are also included in settings.ini, then loadlogin method within views.py is supposed to use the username and password to obtain an access token without using the normal CAS login. However, instead of using the value of IS_DEV_ENVIRONMENT loadlogin is hardcoded with False. This is due to a bug where if it is set to True the access token appears to be obtained, but then the user is redirected to the connect.bioviz CAS login page instead of their dev server. This may have to do with some logic changes we made to logging out the user and redirecting them to connect.bioviz.org whenever an issue is encountered - such as an expired access token.

          Task: Investigate and fix the issue so that loadlogin uses the IS_DEV_ENVIRONMENT variable properly.

            Attachments

              Issue Links

              relates to

              Task - A task that needs to be done. IGBF-2521 Add dev setting to BioViz Connect playbook

              • Major - Major loss of function.
              • Closed

                Activity

                Ascending order - Click to sort in descending order
                Hide
                Permalink
                chaitanya Chaitanya Kintali (Inactive) added a comment -

                Pull Request Link:
                https://bitbucket.org/nfreese/django-cyversedev/pull-requests/195/igbf-2549/diff

                Moving the ticket to Needs testing.

                Show
                chaitanya Chaitanya Kintali (Inactive) added a comment - Pull Request Link: https://bitbucket.org/nfreese/django-cyversedev/pull-requests/195/igbf-2549/diff Moving the ticket to Needs testing.
                Hide
                Permalink
                nfreese Nowlan Freese added a comment -

                Tested using personal AWS account using BioViz Connect ansible playbook. When IS_DEV_ENVIRONMENT in the settings.ini is set to True the user is automatically logged in using the USERNAME and PASSWORD variables in the settings.ini. When IS_DEV_ENVIRONMENT is set to False the normal CyVerse oauth login occurs. I tried this on an ec2 with an elastic ip set to nowlantest.bioviz.org and on an ec2 not associated with a domain name. Both worked when IS_DEV_ENVIRONMENT was set to True. This is useful for future developers as the normal CyVerse oauth login requires a domain name that ends with bioviz.org.

                Closing issue.

                Show
                nfreese Nowlan Freese added a comment - Tested using personal AWS account using BioViz Connect ansible playbook. When IS_DEV_ENVIRONMENT in the settings.ini is set to True the user is automatically logged in using the USERNAME and PASSWORD variables in the settings.ini. When IS_DEV_ENVIRONMENT is set to False the normal CyVerse oauth login occurs. I tried this on an ec2 with an elastic ip set to nowlantest.bioviz.org and on an ec2 not associated with a domain name. Both worked when IS_DEV_ENVIRONMENT was set to True. This is useful for future developers as the normal CyVerse oauth login requires a domain name that ends with bioviz.org. Closing issue.

                  People

                  • Assignee:
                    chaitanya Chaitanya Kintali (Inactive)
                    Reporter:
                    nfreese Nowlan Freese
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    2 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: