Skip to content

Clarify that testing a downloaded profile is only relevant if using Pledge on same platform #31

@aronr

Description

@aronr

Kathy Durkin, in BRC HPC Ticket 357 on 2015-06-15, wrote:

[Due to Firefox issues] I could not make Pledge enrollment work from Firefox 38.x on either Linux 64 bit (Centos 6.x) or MacOS 10.10.x. I did get it to work on Chrome on MacOS.

I will be connecting to Savio from my Linux environment and I had already installed Pledge there, so I skipped the Profile testing in Step 4. That would have required me to install Pledge and create a Profile on my Mac, a step which is not useful for me. I was only using the Mac at that point as a Pledge Enrollment workaround. As written, Step 4 only makes sense if the Pledge enrollment step is being done on the same machine which will be used with Pledge OTP generation.

This might mostly pertain to a situations where someone needs, or chooses, to perform just the web-based Pledge enrollment step on a device, other than the device where the Pledge app will actually be used, but I can clarify with Kathy. (In her scenario, she might have used that second device as a workaround, to issues encountered when trying to enroll from the device she intended to use with Pledge.)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions