Social Login design flaws

  • 1
  • Idea
  • Updated 3 years ago

Just a few thoughts on the Social Login CWP that has been frustrating.

  1. Allow color changes to fonts. White text on white backgrounds doesn't work well at all. Very unsure why black would not be a default text color. Either way, I'm sure most have to stray away from colors that identify their business identity just to accommodate the CWP.
  2. The logon splash is HUGE!
  3.  The TOS checkbox is hidden off-screen due to the login area taking up so much space, and requires visitors to hunt for it, once they first try logging in without checking it.
  4. The CWP is not responsive to mobile devices (screen size), and requires much fiddling to line up the logon area.
  5. Despite the CWP not being responsive to mobile devices, it oddly behaves differently and hides the test boxes for membership authentication, requiring you click "Login with Member ID" before allowing text entry.
  6. There needs to be a way to identify authentication (user) in Hive Manager (outside of just seeing that they logged on to a public SSID).

I would like to roll out this feature, but need assurances that the Social Login platform is still being worked on.

Photo of Jeremy Stewart

Jeremy Stewart

  • 47 Posts
  • 0 Reply Likes

Posted 4 years ago

  • 1
Photo of Jeremy Stewart

Jeremy Stewart

  • 47 Posts
  • 0 Reply Likes

A week and no replies. I'll take a stab that the social login won't be developed on.

Photo of John Hanay

John Hanay

  • 38 Posts
  • 8 Reply Likes
Sorry for the tardy reply but we are working on these issues.  As for #6, there is a Managed column in the Active Devices list in HiveManager where we indicate the source of the device. I believe that will address your request.
Photo of John Hanay

John Hanay

  • 38 Posts
  • 8 Reply Likes
For item 5, can you provide some specific examples and/or the make/model of the devices so we can replicate the issue.
Photo of Bryan Tetlow

Bryan Tetlow

  • 78 Posts
  • 2 Reply Likes
There is a FLAW with the user identification (#6) when using the Social Login logs to add to the HiveManager information.


When a user logs in -- the first time -- you can see the information with no issues.
IF that user has multiple devices, then ONLY the LAST entry is left in the Social Login information screens.  It doesn't matter if you use the User ID, Phone #, or Social Login options.

EACH of those option groups suffers this problem.

The fix for this is to match the login creditials AND the MAC address of each device as a separate entry instead of simply replacing the existing entry with the latest.

Both I and my vendor have been able to replicate this issue.

So, the authentication lists cannot be counted on 100% on their own.

Clients ARE properly noted on the HiveManager side as each client, regardless of how you got connected is unique without exception there.

This was discovered when we had a problem user, and when tracing backwards we found they were not in the Social Login logs that were available.
Photo of John Hanay

John Hanay

  • 38 Posts
  • 8 Reply Likes
Thank you for your feedback....Social Login was designed to only surface the user info for the user. However, your request is valid and we will look into updating the logs to include device information.