Ivan Masár

My feedback

  1. 33 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Ivan Masár supported this idea  · 
  2. 37 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Ivan Masár supported this idea  · 
  3. 8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Ivan Masár supported this idea  · 
  4. 10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Ivan Masár supported this idea  · 
  5. 5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Ivan Masár supported this idea  · 
  6. 66 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Ivan Masár supported this idea  · 
  7. 35 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Summon » Other  ·  Admin →
    Ivan Masár supported this idea  · 
  8. 15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Ivan Masár supported this idea  · 
  9. 17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Ivan Masár commented  · 

    As a Shibboleth IdP administrator I think this really ought not be implemented.

    Shibboleth specifically and intentionally supports only web-based authentication workflow ("The Identity Provider provides Web Single Sign-On capabilities..."). The reason for that is that the user attempting to log in must be able to verify the identity of the login page (domain and certificate). This is not possible in a web view. The web view could easily be a MITM attack.

    Therefore the only way to pair the Word add-in with a RefWorks account should be via a generated password/code (whatever we may call it):
    1) the user logs in via Shibboleth to the RefWorks web UI
    2) the user generates a password/code in the RefWorks web UI
    3) the user logs in via this password/code to the Word add-in

    This is currently supported in the RCM Add-in.

  10. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  RefWorks » Other  ·  Admin →
    Ivan Masár shared this idea  · 

Feedback and Knowledge Base