44 results found

1. photographs

   One of our members does not give permission for her photographs to be used on social media or website. Have made note in Internal Notes, but I wonder whether this should not be flagged on all her event registrations? Could this be done automatically? We ask people at each event, but in this case it is a permanent opt out.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Security / Privacy  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Preventing multiple logins by the same member

   Is there any way to prevent multiple login?

   22 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   26 comments  ·  Security / Privacy  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Transferring sign-in/authentication status to a third party website

   We would like to have our members link to outside web sites (for example to access journal article content), using the WA login. The easiest way to do this is using signed linking, which there is no support for in WA. This could also provide a simple mechanism to provide Single Sign-on support using the WA login.

   For example, WA should be able to create a link such as:

   <a href="pathInfo?originator=originator&identity=identity&timestamp=timestamp&token=signature">

   Where:

   • pathInfo - the destination of the link

   • originator - the name of the service generating the signed link. This would be specified in the link settings.

   • identity - the identity to which the user will be authenticated. E.g. the identity of the society or the user. (perhaps to be specified by the editor setting up the link)

   • timestamp - the timestamp for the signed link, the date and time at which the link will expire. (to specify how long the link should remain valid after creation)

   • signature – an MD5 checksum made up of the parameters, the pathInfo, plus a secret pass phrase.

   We would like to have our members link to outside web sites (for example to access journal article content), using the WA login. The easiest way to do this is using signed linking, which there is no support for in WA. This could also provide a simple mechanism to provide Single Sign-on support using the WA login.

   For example, WA should be able to create a link such as:

   <a href="pathInfo?originator=originator&identity=identity&timestamp=timestamp&token=signature">

   Where:

   • pathInfo - the destination of the link

   • originator - the name of the service generating the signed link. This would be specified in the link settings.

   … more

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Security / Privacy  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Redirect HTTPS to HTTP for Payments Only SSL setting

   For sites that use the "Payments Only" setting for SSL and a custom domain, WA still allows users to access the non-payment pages using HTTPS. That seems convienient, but there are side effects to allowing HTTPS access to an HTTP page. First, if a user does try to access a non-payment page with HTTPS, they will get a browser certificate mis-match warning. As you know, the warning that modern browsers display can be quite scary to the average user. I think you will find this issue to be more common than you think, such as a new site where the site owner has moved from an older all https site to WA and used custom page urls on their key pages. Or hand typed URLs. The second issue this would solve is with Google Webmaster Tools. WMT searches sites that have certificate mis-matches (like my three WA sites) and emails the admin about once a month to warn them about the cert mis-match. This could cause concern with some admins that don;t understand that the mis-match is legitimate and expected. So I am suggesting that when a site is using the "Payments Only" SSL setting, any HTTPS requests be redirected (with .htaccess?) to HTTP. This is really only needed for custom domains, but wouldn't hurt for non-custom domains. Thank you WA for considering this enhancement. Others please comment if you agree.

   For sites that use the "Payments Only" setting for SSL and a custom domain, WA still allows users to access the non-payment pages using HTTPS. That seems convienient, but there are side effects to allowing HTTPS access to an HTTP page. First, if a user does try to access a non-payment page with HTTPS, they will get a browser certificate mis-match warning. As you know, the warning that modern browsers display can be quite scary to the average user. I think you will find this issue to be more common than you think, such as a new site where the… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  Security / Privacy  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close