Library site CAS SSO decommisioning

Things we need to understand:

What will the "login" button on wellcomelibrary.org point at?
What does the user registration flow look like without CAS SSO.
Will DLCS/DDS authenticated items be affected?
Will existing services be affected during any change to remove CAS SSO and for how long (determine with III).

Will social login for digitised content be affected?
If so, can we provide registered users with a list of their bookmarked items?
What UI changes need to be made to:

https://account.wellcome.ac.uk/manage/
https://account.wellcome.ac.uk/manage/register?service=https://wellcomelibrary.org/
https://account.wellcome.ac.uk/manage/link
https://account.wellcome.ac.uk/manage/view
https://catalogue.wellcomelibrary.org/patroninfo/{id}/ (if bookmarks removed)
https://wellcomelibrary.org/account/

Which of the above will no longer be required?

Things we need to do:

Ensure the search on wellcomelibrary.org takes you to https://search.wellcomelibrary.org/
Ensure domain name changes & server updates happen together
Ensure restricted/closed content in UV can still be accessed with library card
Ensure sign-up link on (https://wellcomelibrary.org/using-the-library/joining-the-library/) doesn't take you to account.wc.

Things we need to communicate:

All registered users who have saved digitised items in UV, to inform that service will no longer be available, and to offer opportunity to get a list of their saved items. (If necessary at this stage)
On website with alert, to inform people who have saved digitised items in UV. Create new content page to explain change and privacy benefits.
Library staff: explain reason for change; highlight any new UI or processes

@kenoir These are what we did when switching to SSO. Things have moved on since 2015 so it's not a case of doing this in reverse order but it should help identify things to think about esp around DNS changes and the impact to Sierra and other library systems
https://wellcomecloud.sharepoint.com/:w:/r/sites/it/libsys/Archive/WDL systems/Authentication - keep/2014 Full Single Sign On/Go live/SSO go live steps.docx?d=w9f26b25b05a44c699e6b2df4b52a5e98&csf=1&e=EGfPv6

Additional considerations added to description.

@jennpb do you have access to the CMS for https://wellcomelibrary.org/? Could you update the links pointing to account.wc? For pre-registration.

Yes, I do, and yes, that's easily done.

Access control, DLCS, DDS, CAS SSO
The DDS and wl.org web sites are both clients of SSO via the CAS protocol.
Prior to SSO, wl.org performed some account self-management functions that have now been removed. It really now just services bookmarks, and to allow login from (it seems to the user) any part of the *.wl.org site(s).
The DDS and DLCS interaction is more complex. Through attribute release the DDS acquires information about the user's Sierra Patron account, including their role membership (can they see Clinical Images? Can they see Restricted Images?)
That is, for a logged-in user, the DDS knows what roles they are in. So far, so good.
But the DLCS is independent of the DDS. It serves assets without knowing anything about the web site that interaction was launched from.
When the DDS (or anything else) registers an image with the DLCS, it can also associate one or more roles with the image record. These are properties of the image in the DLCS. They are just strings, and they fall into two categories:

Members of the first category must be configured as belonging to that category. These are roles that the DLCS can enforce itself, without help from any other system. The "Clickthrough" role is in this category - the DLCS can enforce Clickthrough without ever having to know who the user is.
All other Wellcome roles are members of the second category - they require that the DLCS establish its own cookie-based session for the user. In order to do that, the DLCS delegates to a configured Role Provider - which in this case is the DDS.

Assume in this flow the user isn't logged into anything to start with. If they are, some of this will be avoided through short cuts. This flow bridges the IIIF Auth interaction patterns with a third party auth service (in this case, the CAS protocol, but it could be anything).

Implications
...to be discussed.
Links to account.wellcome.ac.uk
There are links to account.wellcome.ac.uk here, too (this is Sierra - these live in an editable template) in Sierra somewhere...

Addressing the initial points, there are two separate things to consider.
If we remove the SSO Server completely, there will no way to view clinical or restricted material without further development (to provide the DLCS with an alternative means of role acquisition - knowing whether a user has "healthcare pro" or "library staff" in their roles). The DDS provides this service for the DLCS, via its SSO relationship with account.wellcome.ac.uk (which is configured to release roles (attributes) to DDS - the diagram above).
But we can remove wellcomelibrary.org from the single sign on services - that is, make it an auth-free zone, it's just an all-open web site. It can't participate in SSO, therefore it can't know whether the user is logged in on catalogue.wl.org or search.wl.org, therefore it should probably completely dispense with the login/logout/my lib acct UI in the top right.
I would need to do some initial investigation before I could estimate what this would take.

What will the "login" button on wellcomelibrary.org point at?
If it's there at all it will point at the new Innovative login page. But because the library web site won't be able to learn about the user's login status on Encore/Catalogue, maybe it shouldn't be there at all.

What does the user registration flow look like without CAS SSO.
Not sure as we can't see this "native authentication" until disabling SSO, but it will be entirely managed within Innovative user interface. The SSO new user UI does more things to create accounts the way we want them than the older Innovative UI did, so we need to find out exactly what this experience is like now in III products and what info it asks for.

Will DLCS/DDS authenticated items be affected?
Yes. Not clickthrough, but the small number of clinical and restricted items. Hence need to maintain SSO until a DDS re-work.

Will existing services be affected during any change to remove CAS SSO and for how long (determine with III).

Yes.

Will social login for digitised content be affected?
Not really, as clickthrough stuff no longer requires any form of account.

If so, can we provide registered users with a list of their bookmarked items?
Yes, we can do this - as a nice HTML page with working snippets, emailed to them

What UI changes need to be made to:
https://account.wellcome.ac.uk/manage/
https://account.wellcome.ac.uk/manage/register?service=https://wellcomelibrary.org/
https://account.wellcome.ac.uk/manage/link
https://account.wellcome.ac.uk/manage/view
https://catalogue.wellcomelibrary.org/patroninfo/{id}/ (if bookmarks removed)
https://wellcomelibrary.org/account/

Which of the above will no longer be required?
Maybe none of them for regular library use, as registration, general account management would happen through Innovative's "my account" rather than Wellcome's account.wellcome.ac.uk.
I don't know what the Innovative equivalent looks like.

Hi
Responding to a couple of Tom's points above:
Tom: What does the user registration flow look like without CAS SSO?
Some of the workflow can be seen in the Sierra test environment as it doesn't use SSO.  III have set-up the III Library CAS post-SSO authentication.
a) Pre-registration - https://test.catalogue.wellcomelibrary.org/selfreg
This page (the self-reg form) already exists from pre-SSO days.  If you register this way, your details get saved to Sierra, but not to SSO CAS (desired behaviour).  I presume this is not a true test though because the SSO CAS is not currently communicating with the test Sierra environment.  At present email hasn't been set-up on the test server, so I don't receive email confirmation.  I need to check what the complete workflow is for this. And what are the compulsory fields and what is the unique field (email address, I think).
b) Full registration process at Admissions Desk
I have tested this from the desk and am able to register and create a library card using the current production environment without SSO CAS (ie it is not using the test Sierra environment):
I have reverted back to pre-SSO procedure which is still in place.  In the scenario below, registration begins in ID Works rather than SSO CAS.  High overview:
Check Sierra for existing record

       Search by surname in Sierra:

a)            If no record is found proceed to Creating a New Card.
b)            If there is an existing record on Sierra proceed to Renewal.
Creating a new card

       In IDWorks complete the template fully from the registration form.

       Capture the image.

       Print the card. This automatically generates a new unique barcode, there is no need to choose whether or not to print a new barcode.

       Printing the card automatically saves the record into Sierra.

       Retrieve record in Sierra and complete address, email details etc

Renewal

       Retrieve existing record in Sierra.

       Update their Sierra record - expiry date, and any changes to address, email etc

       Retrieve into ID Works (cut and paste the p-number/barcode from Sierra)

       Print the new card.

ID Works communicates with Sierra via III's Patron Update Web Service - https://libsys.wellcomelibrary.org:843/iii/patronio/services/PatronIO?wsdl
When the card is printed, it saves into Sierra. It is not in CAS.

The version of the Library site deployed to https://library-uat.wellcomelibrary.org/ no longer has an authentication module in its HTTP request pipeline.
This means you can't authenticate; the site no longer has a notion of a user, you are always anonymous.
I have made various changes to deal with this, including removing login calls to action.
Another change is to https://library-uat.wellcomelibrary.org/account, which is no longer a protected page - but could instead explain what happened to your bookmarks (the content is managed in the CMS).
I have disabled the Add to bookmarks call to action in the UV.
Testing locally with the DDS pointing at the live storage service, I can verify that this works.
However, the library-uat DDS points at the staging storage service, which makes this tricky to test because there aren't that many works in the staging storage. I was testing locally with https://library-uat.wellcomelibrary.org/item/b28079607 but this item is not available in staging storage (it could be pushed there, though).
UAT testing Goobi workflows requires that UAT uses staging storage, but testing the library site without SSO requires that UAT uses production storage, so you can still see everything.
These two variants are supported by the dashboard on various ports, but I'll need to prepare another environment to test this new combination of wl.org without SSO, DDS with SSO, and production storage, unless we don't need Goobi testing for a bit.
Either way, the library site itself (the non-DDS bit) is testable without SSO on https://library-uat.wellcomelibrary.org/.
(note to self for later - the branch no-sso-wlorg is configured for the "Ecosystem-Branch" deployment in TeamCity).

Hi Tom
You said: "Either way, the library site itself (the non-DDS bit) is testable without SSO on https://library-uat.wellcomelibrary.org/."
I'm presuming that you're referring to testing of the library site elements, not the Sierra elements - ie requesting holds etc?  When I go to the webpac from https://library-uat.wellcomelibrary.org/ I get taken to the live webpac.
So, if III have modifed test.catalogue.wellcomelibrary.org to replicate the library CAS authentication (post SSO), how does that get integrated with your library-uat site?  Or does it remain separate and we test the Sierra functionality on the Sierra test server?
Secondly, can you clarify for my benefit the authentication of the bookmarks.  If we previously had to log into the library website in order to bookmark images from the UV, why is this a problem now with the new encore/SSO environment?  Aren't we requiring users to do the same as before the change?
Thanks
Louise

hi Tom, Robert
What is your availability before Christmas for a catch-up to discuss next steps?
I want to make sure that I'm clear about the test environments (my questions above) and what are the remaining tasks so that we can schedule the changes required with III and Platform Technology (infrastructure).
Thanks
Louise

Hi all
For info, I'm attaching a high level summary that I created for my D&T team.  It includes an overview of the broad pieces of work identified.
Louise
SSO problem.docx

The work I have done above removes single sign on functionality from the wl.org site in anticipation of its imminent retirement, rather than convert it to use III's CAS-like endpoint instead of the SSO service.
That is, it's looking to shut bookmarks down, not keep them but with a different auth provider. It makes the wl.org site an anonymous site.
Prior to SSO and DLCS, when the wl.org site and DDS did all of user management, access control and asset delivery, they used III's CAS-like protocol (there were a couple of gaps) but also relied on obtaining specific data about the user from Sierra via the Patron API. It was never just III's SSO mechanism. That code was written mostly in 2012.
When SSO arrived that code got stripped out, and the DDS and wl.org sites used a compliant CAS protocol and attribute release mechanism to acquire user information. However, the DDS does still call the Patron API to get specific further information (is the user a healthcare professional? Are they staff?).
Converting it all to use III SSO would only be feasible now if the III service was completely CAS compliant, and supported attribute release with the same patron attributes released by SSO. I would need to do some work to assess this.
We could just change the CAS configuration to point to III again instead of SSO and see what happens but I would need to allocate some time to assess the result. What version of the CAS Protocol is supported by the III endpoint?

Hi Tom
Thanks.  I'll ask III about which version of the CAS Protocol is supported.
Understood what you say about shutting down the bookmarks to make wl.org an anonymous site going forward.  And for clarity, we are talking about the 'Add to bookmarks' feature in the UV, aren't we?   Sorry to labour the point, but my question is about these bookmarks on the current live site.  One of the concerns about the new Encore/SSO environment was that it would force users to login to look at 'bookmarks'. I presume that we are not talking about these UV bookmarks (as they always did require authentication), but instead we are talking about bookmarked pages like this: https://search.wellcomelibrary.org/iii/encore/record/C__Rb2804734.  There are no other 'bookmarks' impacted by the Encore/SSO https change, are there?
It's a terminology thing and I just want to ensure that I understand what the impact of the new set-up has been.
Thanks
Louise

Ah sorry, yes - I'm talking about UV bookmarks not Sierra bookmarks.
The latter were always out of the scope of the wl.org site. Sorry about the confusion.

Hi Tom
I am awaiting an update from III about the version of the CAS Protocol (the lead engineer is back in the office on Monday).
In terms of testing, is this where we're at?:

https://library-uat.wellcomelibrary.org/ - is currently an anonymous site.  So is testing on this site limited to checking page content for anything that needs updating in terms of new procedures etc?

Updating content - is that done via the CMS on the UAT site?

If you change the CAS configuration to point to III again instead of SSO, what testing will that enable us to do?  Will it allow for testing of Sierra functionality (placing holds, saving searches etc) or just DDS (viewing restricted/clinical images, anything else?)?

When we go live, how do the changes in https://library-uat.wellcomelibrary.org/ get pushed out?  Is the whole site turned into the live site?

Question about: "I have disabled the Add to bookmarks call to action in the UV."
When I search on the UAT site and view an online resource in the UV, I still see the "Add to bookmarks" link (which takes me to SSO account login).  Is that what you mean?

Thanks
Louise

Hi Tom
Re: version of the CAS Protocol - I've had this response from III:
"I believe the CAS used by Innovative for the Innovative library login is  Apereo CAS 5.3. I'm not sure if this is the inforrmation required, if not let me know."
Let me know if you need something else.
Thanks
Louise

Hi Tom
Please could you respond to https://github.com/wellcometrust/platform/issues/4016#issuecomment-565356710 when you have a moment.
thanks
Louise

Hi all
I've checked with TOm and his next availability for a meeting is Mon 21st Jan.
Natalie, Robert - I'll put something in our calendars to meet before then for a quick catch-up and I'll schedule a second meeting with Tom for 21st Jan.
Tom, if you get a chance, please can you respond to https://github.com/wellcometrust/platform/issues/4016#issuecomment-565356710
You asked about the CAS Protocol - I mention above that the response from III was:
"I believe the CAS used by Innovative for the Innovative library login is Apereo CAS 5.3."  Let me know if that's not the info you require.
Thanks
Louise

Hi Tom
Sorry, one other thing.  Is it possible to quantify the impact of removing the UV bookmarking functionality e.g. how many people (not Wellcome employees) have used it in the last 6 months?
Thanks
Louise

Stats:
3272 bookmarks made by 632 distinct users.
Of these, 129 users have made 5 or more bookmarks, and 24 have made 20 or more.
The most bookmarky user has made 335 bookmarks. That's @jennpb.

Please let me know if further development on the UAT to integrated with CAS is a no-go because of resource/cost factors

I think that given the limited lifetime of wl.org, it probably is a no go.

https://wellcomelibrary.org/account/
remove all references to this page and make it inactive.

This was the editorial and template work required in CM7 / wl.org I mentioned. It's not a webpac page - I've done the equivalent for this page on library-uat.wellcomelibrary.org but not in a way you would want any real users to see.

changing the button label to My library account

We can change this when making the template changes above, and anything else that helps avoid confusion. That top-right space used to represent account and login calls to action, but now it doesn't, and needs to look not-broken, for which that text change might be enough.
Agree that PDF not the best way to send people their bookmarks.
The following questions might seem over-complicating the issue but there are several ways in which this could work in practice with varying effort required.
If a list of links, is that just an HTML-body email? Or is it a page hosted on the newly non-access-controlled wl.org with some kind of security-through-obscurity URL like a Google doc? Either way, I assume something like this:

Your Bookmarks
Your Folder 1
Bookmark 1
[Thumbnail of selected area, optional] [Link to page and region]
The note you made about this bookmark (if you made one)
Bookmark 2
[Thumbnail of selected area, optional] [Link to page and region]
The note you made about this bookmark (if you made one)
Your Folder 2
Bookmark 3
[Thumbnail of selected area, optional] [Link to page and region]
The note you made about this bookmark (if you made one)
Bookmark 4
[Thumbnail of selected area, optional] [Link to page and region]
The note you made about this bookmark (if you made one)

These links to wellcomelibrary.org/item/bnumber#page/region are in this case from the site-managed bookmarks but will also work for all the other bookmarks made by people that do the same thing - no matter where they have made them. I assume that there will be a skeleton redirecting app handling wl.org/item page requests, that will take the user to the equivalent view on wc.org...
If I click my bookmark:
https://wellcomelibrary.org/item/b28047345#?c=0&m=0&s=0&cv=160&z=-0.0072%2C0.4929%2C1.1098%2C0.5615
At some point when wl.org is retired, this will get redirected to:
https://wellcomecollection.org/works/km3uczhf/items?canvas=161&sierraId=b28047345&langCode=eng
(which will ignore the specific region, but lands on the right page)
That is, links sent to user for their stored bookmarks, or links anywhere out there on the web, link as now to the UV but can later be redirected to their equivalent wc.org work/canvas page.
Or, the links that get sent to users requesting bookmarks could be made to go straight to the equivalent wc.org page (but archives...)
What's the process of sending the links to those who ask for them?
Is there a dynamic process that generates the HTML email on-the-fly and sends it? Or are you cutting-and-pasting some HTML that was made from the bookmarks in a one-off export and stored somewhere secure? Or both of these - generate the HTML on the fly, for whatever purpose which might include pasting into an email.
Proposal for the non-comms parts of this process, to make this as easy and flexible as possible to service requests from users:

I generate an export of all the bookmark data in a form that can be used to generate HTML emails but also can be re-purposed for other uses later if something unforeseen comes up - that is, easy for you do do something else with it.
I create a web page not on wl.org but on some other webapp; this is restricted to Wellcome staff; it has access to the bookmark data and will respond with the simplest possible HTML in the format above if given a user's email address.
A user requests bookmarks; someone with permission goes to this page, gets the bookmarks for that user's email, and pastes them into a new email message - adding whatever friendly text is required for the context of the enquiry.
Option - the web page itself sends the email to the user, with room for a custom message.

Thanks, Tom, for this detailed work.
Bookmarks

Proposal for the non-comms parts of this process, to make this as easy and flexible as possible to service requests from users:

I generate an export of all the bookmark data in a form that can be used to generate HTML emails but also can be re-purposed for other uses later if something unforeseen comes up - that is, easy for you do do something else with it.

I create a web page not on wl.org but on some other webapp; this is restricted to Wellcome staff; it has access to the bookmark data and will respond with the simplest possible HTML in the format above if given a user's email address.

A user requests bookmarks; someone with permission goes to this page, gets the bookmarks for that user's email, and pastes them into a new email message - adding whatever friendly text is required for the context of the enquiry.

Option` - the web page itself sends the email to the user, with room for a custom message.

@kenoir @pollecuttn  What is your opinion of Tom's proposal.  What team would be responsible for  doing the leg work of responding when a request for bookmarks is received?
Login
Jenn, Tom - are you proposing the Login button on the WL site remains in place but:

links to the libsys login (which would only take them to their My Library Account page)
That the label changes from 'Login' to 'My Library Account'?

@louisesimon Yes, this is fine. The Platform team will deal with this on an ad hoc basis as/when any requests for this come in.

I had a meeting with Simon D, Danny and Sophie yesterday about comms etc.
Like Jenn, they are of the opinion that it would be a better user experience for the existing Login button on the Library homepage to go to the libsys login.  As noted this would take them to 'My Library Account' page, but it would only be one click to take them to the library home page.  They don't even propose changing the Login button name.
@pollecuttn @kenoir  @tomcrane What are your thoughts?

All other things being equal I prefer @jennpb's suggestion of "My library account" - as the text of the "Login" button will now never change on wl.org (it doesn't know whether you are logged in "over there") but the call to action in that space will change in the Innovative parts. Depends how you look at it though.

@tomcrane So just so that I have this clear.
Currently with SSO, the buttons in top right are:

Before login:
JOIN     /        LOGIN

After login:
MY LIBRARY ACCOUNT    /    MY BOOKMARKS    /     LOGOUT

Post SSO, if no change made to button text:

Before login:
JOIN    /      LOGIN

After login:
LOGIN  /  LOGOUT   [with the assumption that MY BOOKMARKS would be removed]

Post SSO, if change made to button text:

Before login:
JOIN    /   MY LIBRARY ACCOUNT

After login:
MY LIBRARY ACCOUNT  /    LOGOUT    [with the assumption that MY BOOKMARKS would be removed]

If the user chose to delay logging in until they reached an Encore search page / webpac/ or were prompted to after clicking to request an item, would that make a difference?  i.e. would they be logging in via libsys?
Currently, if you login via libsys: https://libsys.wellcomelibrary.org/ , you see:

Before login:
JOIN /   LOGIN

After login:
MY LIBRARY ACCOUNT  /    LOGOUT

ie text changes from Login > My Library account
Thanks
Louise

I imagine it would look like this:
Pre-login

Post-login

Thanks for confirmation, Jenn.
@kenoir @pollecuttn Your thoughts?  I'd need to run this past LE&E too.
And my question about delaying login until webpac, encore or closed stack requests - if that makes a difference to the buttons they see (ie do they ever get to the libsys version of the buttons)?

Happy to go with what Jenn says.

Hi all
Update:

Simon Demissie is okay with the text change to the Login button being 'My Library Account'.
I've met with Simon, Danny and Sophie to discuss comms.
Meeting with Natalie next week to make the webpac changes to staging.
As stated above, Platform Technology will send out the Bookmark URL links to users who request them.

Next steps

Due to illness etc,I'm still awaiting confirmation of how long the notice period will be for people with Bookmarks.  Once decided we can schedule the change with III and D&T.  I have a comms meeting next week, all being well, but hope to get an answer before then.
@tomcrane How much time do you need to schedule the work on the UAT site login/logout buttons  (https://github.com/wellcomecollection/platform/issues/4016#issuecomment-582867583)? That is:
i)  Re-instate on UAT site (currently anonymised).
ii) Change text from 'Login' to 'My Library account'
iii) Link the button to https://catalogue.wellcomelibrary.org/iii/cas/login
iv) The My Bookmarks link that currently appears after logging in should be removed.
Schedule changes with Jenn to Library website CMS (already identified)
Comms group will formulate text to go out to users of Bookmarks.
@tomcrane Will you be able to output a list of all the users and email addresses with Bookmarks?
The Bookmarks page and Links page will need to be removed/made inaccessible.  Is that one for you, @tomcrane , or Jenn?

Thanks
Louise

Notice period for Bookmark users
Simon Demissie  and Danny Birchall have agreed on 3 weeks notice.
Platform Technology's next sprints are:
Sprint 11	06/04 - 17/04
Sprint 12	04/05 - 15/5 (there's a firebreak in between)
Simon and co think that sprint 11 is feasible.  If we went with the second week of their sprint (wc/ 14 April because of Easter), does that sound feasible to you all?
@tomcrane - how soon would you be able to output the names and addresses of the users with bookmarks?
Brief summary of tasks for Tom, Jenn, Natalie/Robert before go live:

@tomcrane  Output names and addresses of the users with bookmarks.
@tomcrane to reinstate /make changes to the login button as described in  https://github.com/wellcomecollection/platform/issues/4016?email_token=AAMOSFJ4OJ72VNSBHZDVGCDRBP2AFA5CNFSM4JHLWY32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEK65U7Y#issuecomment-591865007
@tomcrane  or @jennpb ?  Make inaccessible/remove the Bookmarks  page and Links page inaccessible. Not sure who this would fall under.
@jennpb to make changes to Library website via CM7 (limited to a 4 or 5 URL changes).
@pollecuttn @kenoir Digital Engagement to draw up process for sending out Bookmark links to users that request them as outlined by Tom  #(https://github.com/wellcomecollection/platform/issues/4016?email_token=AAMOSFJ4OJ72VNSBHZDVGCDRBP2AFA5CNFSM4JHLWY32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEK65U7Y#issuecomment-581915379)
Anything else?

N.B.
I'm creating a comprehensive task list and will circulate, but just wanted to get feedback from you on whether timeframe for above tasks is realistic.
Thanks
Louise

Hi all
My tasks, I think:
a) Disable bookmarking functionality in UV (the UI will no longer offer this option). Do you want to warn people that this will be going, or should we just remove it? This is not the same as removing people's access to their bookmarks, just their means of creating new ones. I can do this at short notice, it's basically a UV configuration change.
b) (addressing points 1 and 5 in preceding comment) Create a simple password-protected webapp for internal deployment that:

lists names and email addresses of users with bookmarks, so they can be contacted
for each user, links through to a list of those users' bookmarks, so that if one of those users asks for their bookmarks, the Platform team can paste them into an email and send them.

This task does not have any dependencies and can be done before 14 April. It doesn't affect what site users can see or do.
c) (point 2 in preceding comment)  This would just say "MY LIBRARY ACCOUNT" always, as there is no post-login state on the CMS-managed parts of wl.org, it will be an anonymous site.
d) (point 3 in preceding comment, specifically https://wellcomelibrary.org/account/)
from https://github.com/wellcomecollection/platform/issues/4016#issuecomment-579373838:

Jenn thinks we should remove all references to this page and make it inactive. For users expecting to see the bookmarks option on their 'My Libraryaccount' page, she suggests a "Looking for bookmarks? - Go here" message.

Even if there are no active links to it, people landing here, or any path under it (e.g., if they have bookmarked their bookmarks) will still need to see something. The unfriendly thing would be the standard site 404 page, the friendlier thing would be some editorial content explaining that there's no account-related stuff here any more. This was the mockup I made on library-uat but it needs some template and copy work, although not much.
e) (point 3 in preceding comment, specifically https://account.wellcome.ac.uk/manage/link)
This page is part of the SSO platform; if it is to be removed that would be done by @danielgrant
f) Later (when wl.org is retired), a redirector that works for anyone who has ever bookmarked, cited or otherwise linked to any digitised content on wl.org. Links made by using the wl.org bookmarking feature will be a tiny tiny subset of all the links to digitised material on wl.org in blog posts, tweets, emails, etc. - but they are still regular links so will be handled by this. See https://github.com/wellcomecollection/platform/issues/4016#issuecomment-581373952, about halfway down, for details. Redirects go to the equivalent view on wc.org.
This needs some wider planning as part of the complete retirement of wl.org, so is a separate issue, but needs to be flagged. No point sending someone their bookmarks if the next day is wl.org retirement day and they don't go anywhere.

Hi all
Hope you're all well.
So after yet another hiatus of unprecendented magnitude, let's reconvene.  Given the 3-week notice for comms to library users, I would like to make the change in Platform Technology's sprint 12 - 2 weeks beginning 4 May (there is a firebreak before this).
With regard to Tom's response above

a) Disable bookmarking functionality in UV (the UI will no longer offer this option). Do you want to warn people that this will be going, or should we just remove it? This is not the same as removing people's access to their bookmarks, just their means of creating new ones. I can do this at short notice, it's basically a UV configuration change.

Yes, we need to warn people that  the bookmarking functionality will be going, which will be part of the 3-weeks' notice.  Simon D has confirmed that he is still happy to go ahead with the revised schedule./

b) (addressing points 1 and 5 in preceding comment) Create a simple password-protected webapp for internal deployment that:

lists names and email addresses of users with bookmarks, so they can be contacted
for each user, links through to a list of those users' bookmarks, so that if one of those users asks for their bookmarks, the Platform team can paste them into an email and send them.

This task does not have any dependencies and can be done before 14 April. It doesn't affect what site users can see or do.

@pollecuttn Would it be DE who would send out the emails?  Simon D and Danny are drafting the text of the email which I can provide you with shortly.
@tomcrane  When would be able to create the webapp?  We have a little more leeway now with time.  The latest that the message should go out to users is 13 April, but hopefully before that.

c) (point 2 in preceding comment) This would just say "MY LIBRARY ACCOUNT" always, as there is no post-login state on the CMS-managed parts of wl.org, it will be an anonymous site.

@tomcrane Do you make the change on the UAT site and then push to live?

Even if there are no active links to it, people landing here, or any path under it (e.g., if they have bookmarked their bookmarks) will still need to see something. The unfriendly thing would be the standard site 404 page, the friendlier thing would be some editorial content explaining that there's no account-related stuff here any more. This was the mockup I made on library-uat but it needs some template and copy work, although not much.

d)

Even if there are no active links to it, people landing here, or any path under it (e.g., if they have bookmarked their bookmarks) will still need to see something. The unfriendly thing would be the standard site 404 page, the friendlier thing would be some editorial content explaining that there's no account-related stuff here any more. This was the mockup I made on library-uat but it needs some template and copy work, although not much.

Understood.

f) Later (when wl.org is retired), a redirector that works for anyone who has ever bookmarked, cited or otherwise linked to any digitised content on wl.org.

Understood.
@tomcrane As regards the tasks (account login button, bookmark landing page etc), can you confirm that the current time line gives you enough to schedule this work?
I am drafting a list of go live tasks and will circulate it shortly for comment.
Thanks
Louise

@louisesimon I've not been in any of the comms discussions so I don't know the answer to this. Someone in those comms discussions should be able to tell you.

Hi @pollecuttn
So the reason I was asking you was because it was agreed earlier that DE would send out the bookmark URLs to users who requested them.  They would need access to Tom's Webapp to do this.  It is the technical one-off process of sending out the initial emails to all users that I am now asking about.  Would this be a task for DE as they would have access to the bookmark app?  LE&E are providing the text to be inserted in whatever technical process is being used to send out the emails.

@louisesimon Do you mean from your conversation with Jenn https://github.com/wellcomecollection/platform/issues/4016#issuecomment-579373838 ?
If so, it sounds like the email would be from her.

No no no, please! I don't have anything to do with sending out emails to the public. I thought this was being handled as part of the Comms plan (which I'm not part of), so someone who is not me should have a plan for communicating with the users.

Hi all
No.  I don't mean that.  Ok, sorry not to be clear.
In Tom's response, he said that he is creating a webapp that will contain all the users and emails of those with bookmarks.  My question is who will actually do the technical bit of using the app to send the initial emails?
Comms group have agreed the notice period and will word the email.  We haven't yet agreed the process of sending out the initial emails because the technical mechanism wasn't in place.
If you think that it isn't one for DE, then LE&E or l will have to use the webapp.  It just felt that as DE had already agreed that they would be responding to requests for users to send out URL links (and they would have to use the webapp),  then it would make sense for them to do the initial sending out of emails.
Happy to discuss.
Louise
Get Outlook for Androidhttps://aka.ms/ghei36

From: jennpb<EMAIL_ADDRESS>Sent: Thursday, March 26, 2020 4:52:08 PM
To: wellcomecollection/platform<EMAIL_ADDRESS>Cc: Louise Simon<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [wellcomecollection/platform] Library site CAS SSO decommisioning (#4016)
No no no, please! I don't have anything to do with sending out emails to the public. I thought this was being handled as part of the Comms plan (which I'm not part of), so someone who is not me should have a plan for communicating with the users.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fwellcomecollection%2Fplatform%2Fissues%2F4016%23issuecomment-604544053&data=02|01|l.simon%40wellcome.ac.uk|77059b01780440d039e708d7d1a6064d|3b7a675a1fc84983a100cc52b7647737|0|0|637208383303042886&sdata=CS2Dt7NYKZjrK5bNmdB9MIIkfIcmhNijnKmpVtJkzas%3D&reserved=0, or unsubscribehttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAMOSFJZPHBPAWUIZN25OC3RJOB3RANCNFSM4JHLWY3Q&data=02|01|l.simon%40wellcome.ac.uk|77059b01780440d039e708d7d1a6064d|3b7a675a1fc84983a100cc52b7647737|0|0|637208383303052869&sdata=K48KQfkkXK%2BbwPJbstd93LvQAB2q%2F0U2O%2BrLSrXFBAQ%3D&reserved=0.

Re: my comment above, when I refer to the 'initial emails', I mean the email that will inform users that the Bookmark function is to be removed

@louisesimon I think I'll need a couple of days clear to do all these tasks and prep for tasks that are dependent on others. I'll need to get back to you on scheduling, our schedules are being rearranged a lot at the moment. At time of writing it was assumed that the app mentioned would be deployed somewhere internal to Wellcome's network, does everyone WFH change that?

Hi @tomcrane
THanks.  I'll wait to hear from re: schedule.  The latest we could leave the sending out of the emails to Bookmarks users would be Mon 13 April.  Do you think you'd be able to schedule the webapp by then?
THe other pieces of work(e.g. login button etc) can be pushed back (deadline 4 May, but ideally before then for testing etc).
As regards deploying the webapp onto the Wellcome internal network, I don't think that would be a problem, but could you give me a brief description of what you have planned and I'll run it past out Platform Tech team.
Thanks
Louise

@louisesimon Monday 13 April is Easter Monday (a bank holiday)

@louisesimon Monday 13 April is Easter Monday (a bank holiday)

Thanks, Natalie.  @tomcrane Deadline would be Tuesday 14 April for the webapp, but if we could have it by Thurs 9the, that would be great.
Thanks
Louise

Hi @tomcrane
I commented:

As regards deploying the webapp onto the Wellcome internal network, I don't think that would be a problem, but could you give me a brief description of what you have planned and I'll run it past out Platform Tech team.

If you could give me a response so I can take up with Platform Tec, that would be great.  Also can you confirm if deadline of 9th April is doable?

All,
I've scheduled the DNS change with Platform Tech for fortnight beginning 4th May (sprint 12).  Exact date to be confirmed.

So Platform Tech have changed their sprint dates.  We now plan to go live w/c 18 May.
I'm compiling a task list of remaining work before the go live day and actions to be completed on the go live day.  Attached is my draft so far.
Task list and schedule.docx
A couple of qyestions please:
@tomcrane Once you've made the changes to the UAT site, I presume you push these out to live on the day?  Can you let me know your availability for w/c 18 May (I'm thinking Tues 19th if possible).
@jennpb I'm attaching the content changes we identified.  Would you make these changes in advance and publish them on the go-live date?
Website changes.docx

@louisesimon I still don't have remote access to CM7, Mark Gee was supposed to be sorting me out with something. Given this is unlikely to happen, I'll have to coordinate with someone who can still access CM7 on the go-live date.

Confirming my understanding of the process:

Email will go out to users; ASAP afterward Tom will disable the Bookmarks function in the UV so we don't acquire additional users
Some changes will be made to the pages that are hard-coded, in advance of moving over to the Sierra account - Tom and Jenn liaising on this
On wellcomelibrary.org web pages that are content managed in CM7, changes will need to be made on the day (w/c 18 May) as there is no staging area for live, published content. Jenn will need to screenshare with someone who has CM7 access (if she doesn't) to guide them through the process.

On wellcomelibrary.org web pages that are content managed in CM7, changes will need to be made on the day (w/c 18 May) as there is no staging area for live, published content. Jenn will need to screenshare with someone who has CM7 access (if she doesn't) to guide them through the editing process.

Thanks, Jenn.  I'll update the task list.  I understand your access to CM7 is being looked at right now.

Hi @louisesimon
Regarding "Can you let me know your availability for w/c 18 May (I'm thinking Tues 19th if possible)."
The changes to the library site can happen before the access control changes to Sierra. As we are anonymising the wl.org site, and removing one of its external dependencies rather than introducing anything new, I would even prefer that this is done sooner - it can be done as soon as everyone is happy with the behaviour of the site on UAT, rather than have it wait for actions by anyone else.
The fewer time-critical dependencies the better!
I am available all that week, should anything come up.
Tom

Hi Tom
So if you made the changes before the DNS changes etc, what would happen when you clicked on Login (or ‘My Library Account’ as it would be called then)?  Whilst https://catalogue.wellcomelibrary.org is still pointing to the SSO server, presume you’d still go to SSO?
If you get a chance, could you also respond to my questions about Bookmarks in my email response from yesterday.
Thanks
Louise
From: Tom Crane<EMAIL_ADDRESS>Sent: 21 April 2020 08:54
To: wellcomecollection/platform<EMAIL_ADDRESS>Cc: Louise Simon<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [wellcomecollection/platform] Library site CAS SSO decommisioning (#4016)
Hi @louisesimonhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flouisesimon&data=02|01|l.simon%40wellcome.ac.uk|91b97590d84f4fb12ef208d7e5c916ef|3b7a675a1fc84983a100cc52b7647737|0|0|637230524141981056&sdata=oFaJc2UiLeOL9guELqk%2Bcd%2FL55ZzSP8keOCmK7HOx1Y%3D&reserved=0
Regarding "Can you let me know your availability for w/c 18 May (I'm thinking Tues 19th if possible)."
The changes to the library site can happen before the access control changes to Sierra. As we are anonymising the wl.org site, and removing one of its external dependencies rather than introducing anything new, I would even prefer that this is done sooner - it can be done as soon as everyone is happy with the behaviour of the site on UAT, rather than have it wait for actions by anyone else.
The fewer time-critical dependencies the better!
I am available all that week, should anything come up.
Tom
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fwellcomecollection%2Fplatform%2Fissues%2F4016%23issuecomment-617016836&data=02|01|l.simon%40wellcome.ac.uk|91b97590d84f4fb12ef208d7e5c916ef|3b7a675a1fc84983a100cc52b7647737|0|0|637230524141981056&sdata=j7JEaBwrhE6z%2BBfkLTQ8tCY7s0hd1WiSaaXZnNY2h2s%3D&reserved=0, or unsubscribehttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAMOSFL36RECEEHE64G2ELLRNVGHXANCNFSM4JHLWY3Q&data=02|01|l.simon%40wellcome.ac.uk|91b97590d84f4fb12ef208d7e5c916ef|3b7a675a1fc84983a100cc52b7647737|0|0|637230524141981056&sdata=dhIliYIcHMjbOy4yoLJHq7NFhVR9USKdKJSRJJngR9A%3D&reserved=0.

So if, as you propose, [the changes to the UAT site went live] before the DNS changes etc, what would happen when you clicked on Login (or ‘My Library Account’ as it would be called then)? Whilst https://catalogue.wellcomelibrary.org is still pointing to the SSO server, presume you’d still go to SSO?

HI @tomcrane Please could you respond to the above.
Thanks
Louise

This is odd, I wrote a chunk of text about this was sure it was a comment here, on this issue. I'll see if I can work out where it went. Does anyone have it in an email notification?
Anyway, the gist of it was that you'll go to whatever page the target of the link uses for login. If we make it link to https://catalogue.wellcomelibrary.org/patroninfo/ then Sierra will (if you're not logged in) bounce you to SSO for now, and to its own login page after the changeover. The library end of it doesn't need to know when that happens.

Hi @tomcrane
That's strange. No, I didn't receive an email notification on your missing comment.
Understood, re: library login.  So can you confirm that, to the library user, the only difference they'll see is that the Login button is now labelled 'My Library Account'?  Once that's confirmed, I'll let the Library know.
If it is live before the changes to the Webpac pages go live, the account page will still mention linking accounts (with social media accounts) which will no longer be possible.  Depending on how near to go live we are, I may just leave the links in there, as the info will be removed as part of the webpac changes for go-live (Linking accounts is so little used).
All, here's a summary of where we're at regarding tasks that impact on Tom

Go live (ie switch from CAS SSO to Sierra login) will be week commencing 18 May.  Hopefully Tues 19 May TBC.

Simon D (on behalf of Comms team) will send out the email to Bookmark users.  He says today (24th) or Monday 27th.
@tomcrane I'll confirm with you as soon as I know so that you can disable the function to make new bookmarks (the day after the email goes out as discussed).

@tomcrane - I'll schedule with you, making live the UAT change (ie anonymising the site and having the login relabelled to My Library Account).  The nearer to the go-live day the better.

@tomcrane  - the other tasks I had noted for you were:
i)	Remove access to existing bookmarks.  This would need to be done at the end of the 3 week notice period (c18 May).
ii)     Change content of Bookmarks page (https://wellcomelibrary.org/account/)) to explain content and function no longer available etc (Editorial input required).  To be done same time as i) above.
It currently displays some place-holding text on UAT: https://library-uat.wellcomelibrary.org/account.
@jennpb - presume the wording of this page is one for Danny B and the comms team?

Let me know any questions about this.
Thanks
Louise

@louisesimon No, I can do the interface copy. Already been discussing it with Tom, I just have a few more detailed questions for him about the account page.

@jennpb Thanks.  I'll update my task list

@tomcrane Simon has confirmed that he will be sending out the bookmark email tomorrow (28th).  Will you be able to turn of the function to create new bookmarks the day after?
Thanks

Hi @louisesimon - yes, I can disable that feature in the UV.

Hi @tomcrane
With regard to my message above - https://github.com/wellcomecollection/platform/issues/4016#issuecomment-618861352 -  please can you respond my question in para 2 (I've made it bold).  Also, please can you respond to 4a and 6.
Thanks
Louise

can you confirm that, if you make live the UAT changes before the SSO switch day, the only difference the library user will see is that the Login button is now labelled 'My Library Account'?

This button will just be a fixed link to the Sierra account page (second pic in https://github.com/wellcomecollection/platform/issues/4016#issuecomment-552664200)
They will no longer be able to see their bookmarks after this change too, of course - the wl.org site will now be anonymous. So I can defer making this change to allow for the three week window.

At a meeting wayback, you said that users with access to restricted content in the UV would still have access as you would keeping the SSO element for that purpose. Can you confirm that is still the case?

That was my suggestion, yes. However, after discussing this with @danielgrant recently, I am going to do a little spike to see whether I can just have the DDS authenticate against Sierra directly using Sierra APIs (pintest) for this one scenario - i.e., borrow the login screen front end code from SSO and have it presented by a page served by the DDS. Although this means a bit more development in the DDS, it means SSO is then completely retired, so no need to worry about account linking pages or trying to keep a complex app running for this one important but not-often-used scenario. The only scenario in which a user would be required to authenticate is for viewing clinical or restricted content, for which they need a full Sierra account (not a social login).
This would mean SSO has no client services, and could be switched off. It also makes future transition of the DDS easier. Fewer spinning plates.
For this and 4a - I don't have a definite date to do this. I am going to have to fit it in somewhere over the next few days. I will get back to you soon on this.

THanks, @tomcrane .  All understood.  So let's defer making the UAT site live to allow for the bookmarks notice period.
I'm afraid that I'm going to have to delay turning off the create bookmark feature as Simon D still has some questions about registration processes and how they will operate in the post-SSO world (had meeting with him today).  They are also registering users remotely at present (hadn't been communicated to me) so I need to formulate the process post-SSO.
I hope that this won't delay our existing go live date of 19th Nov as Simon says he is okay with having a shorter bookmark notice period.
The bottom line is that I will let you know @tomcrane when you need to turn off the create bookmark function.
Please continue with the UAT work with the assumption that we will go live on 19th May.
Thanks
Louise

Hi @tomcrane
Just having a mental blip on an the account buttons post SSO.  Can you confirm that the Logout button shown in Jenn's mockup atLhttps://github.com/wellcomecollection/platform/issues/4016#issuecomment-582867583 will indeed display?
If the site is anonymised and the 'My Library account' is effectively just a link to libsys login, will it still be able to generate the Logout button on the library pages?
Thanks
Louise

Hi @kenoir
Do you know yet how users will authenticate on the Wellcome Collection website - requesting material from closed stack etc?  Presume it would have to be via Sierra?
Checking in case staff ask at the briefings I have lined up.
Thanks
LOuise

@louisesimon
I should have been clearer there. It got lost in https://github.com/wellcomecollection/platform/issues/4016#issuecomment-598847734.
The logout button will not display, because the wl.org site will be anonymous. It doesn't know who you are or whether you are logged in over in Sierra.
Whatever appears in the top right will be the same all the time.
Currently in the anonymous version this is the two links:
[ JOIN ]  [ MY LIBRARY ACCOUNT ]
... which go to:
https://wellcomelibrary.org/using-the-library/joining-the-library/ and
https://catalogue.wellcomelibrary.org/patroninfo/
That doesn't mean the user will always see the same thing when they follow the second link, though. This goes to the patron info page in Sierra. If they are already logged in over there, they'll get their user info page. If not, Sierra will put its own login screen in their way.
Obviously these links can be whatever we want them to be, but they can't adapt to the user's logged-in-ness over in Sierra.

Thanks, Tom.  Understood.  That's what I thought when I came back to look at this a second time.

Hi @tomcrane
Comms sent out the message about Bookmarks yesterday so please can you turn off the function to create new bookmarks.

All
The DNS change (D&T)  and configuration changes (III) will take place on morning of Tuesday 19th May.
@tomcrane @jennpb Please can we coordinate the UAT site going live and the text changes to the site.  I know that you have been working together on the latter.
Thanks
Louise

@tomcrane @jennpb  - just nudging you about above comment re: coordinating UAT site and text changes going live.  Please can we agree a plan.  Thanks

Creation of new bookmarks now disabled in UV.

Here's the updated plan:
On 19 May:

@tomcrane will make template and text changes to wellcomelibrary.org/account. I've provided the text to him already.
@tomcrane will make changes to the Restricted Content login page. My suggestions are in the Google Doc
I will make the website changes via CM7

Page
Where to make change
Change required
Details

Joining the library https://wellcomelibrary.org/using-the-library/joining-the-library/
CM7 - Add new link to Link Roster; Edit link on page; Delete account.wellcome.ac.uk link from Link Roster
Pre-registration link
Change from: https://account.wellcome.ac.uk/manage/register?service=https%3A%2F%2Fwellcomelibrary.org%2F to https://catalogue.wellcomelibrary.org/selfreg

Computers, printing and wifi https://wellcomelibrary.org/using-the-library/services-and-facilities/computers-printing-and-wifi/
CM7 - Add new link to Link Roster (if needed); Edit link on page
Mobile print; Library account link
Change Library Account link to https://catalogue.wellcomelibrary.org/patroninfo/

And for @louisesimon -
This is not absolutely time critical but can happen soon after the changes above.

I will add a rule to the wl.org estate that redirects any sub path of wellcomelibrary.org/account back up to wellcomelibrary.org/account. This handles any direct links to bookmarks that people might have made (rather than them seeing a 404 page).
???* will change the routing for account.wellcome.ac.uk so that all requests for that hostname (whatever the path) will be redirected to wellcomelibrary.org/account. This explains what just happened if there are bookmarks or any other links hanging about that go to the SSO site.

The latter redirect shouldn't happen within the account.wellcome.ac.uk estate because we want to switch all that off. It should happen at the load balancer, I suppose.
*sorry for the ???, don't know who will do this bit.

???* will change the routing for account.wellcome.ac.uk so that all requests for that hostname (whatever the path) will be redirected to wellcomelibrary.org/account. This explains what just happened if there are bookmarks or any other links hanging about that go to the SSO site.

I'll open a ticket with Platform Tech to do this redirect after then switch

Thanks @jennpb

I will make these website changes via CM7

I identified one additional change which I omitted from my list to you, Jenn.  Please can you add the following to you list of CM7 changes:

Request and delivery   https://wellcomelibrary.org/using-the-library/how-to/request-and-delivery/
CM7
‘Register online’ link
Change   from:        https://account.wellcome.ac.uk/manage/register?service=https%3A%2F%2Fwellcomelibrary.org%2F   to   https://catalogue.wellcomelibrary.org/selfreg

Thanks
Louise

@tomcrane:

When will you push the UAT site to live?  On the 19th?  As regards infrastructure tasks on the 19th May: Platform Tech will be making the DNS changes early (confirming 8am) and then III have about an hour's worth of config changes to make.

In the Google Doc - Re: the Restricted content login page (https://library-uat.wellcomelibrary.org/iiif/dlcslogin).  Are you happy for me to edit the page to add the URL links (currently showing as 'tbc')?

@louisesimon -

Yes, I can do it on the 19th - I have marked it in my calendar and am flexible about when I do it, so when you're ready just send me a message.
Yes, please do! I have a couple of changes to make to that at some point before next week, for Jenn's edits, but I won't do that today. There are the three "tbc" in a group, and there's also one in the tips on line 119.

@tomcrane: with regard to the linked accounts page - https://account.wellcome.ac.uk/manage/link -
if the host name redirects to wellcomelibrary.org/account as described in comment above, will the linked page also redirect to /account?  If so, it would be good to have some text on /account informing users that linking account feature is no longer available.

I don't think that's necessary to maintain a good user experience during this transition. Linking accounts is a one-time only action, meaning that it's not a page that people would have bookmarked or would actively seek to come back to. I don't believe it's good practice to inform users of services that aren't available if it was for the purpose of supporting a decommissioned service. It just adds more complexity to the messaging.

Hi Jenn.  Understood.  I'm trying to ensure that users who've linked their accounts know that they can only log in with their library account in future.  Take your point that the page is for the process of linking accounts.  Alternatively, I could just add some explanatory text in the My Library Account help page.
For users who sign in with social media account to view bookmarks, then we're covered by the text on the /account page.

@tomcrane Sorry for all the questions this morning!  One more -
I can see that you've made the change to the Login button on UAT .  As agreed, it is labelled My Library Account and directs to
https://catalogue.wellcomelibrary.org/patroninfo/.
I know that there will no longer be a Logout button on any Library pages, but please can you confirm for my benefit that https://catalogue.wellcomelibrary.org/patroninfo is a Sierra page so they will see the Logout button here.

Yes, I can do it on the 19th - I have marked it in my calendar and am flexible about when I do it, so when you're ready just send me a message.

Thanks, @tomcrane .  How long does it take for UAT to go live once you press the button?  Instant?

Not quite instant.
I'll be deploying both the DDS and the wellcomelibrary.org site, x 2 because each has two instances. This takes the TeamCity build server a few minutes to grind through.
So minutes, but not hours.
Although there's nothing really preventing us pushing the anonymised site first. It doesn't depend on Sierra changes. It might even be preferable to to do it that way. On Monday evening, for example.

Hi @tomcrane .  Yes, I think it would be a good idea to push out the anonymised site on Monday evening.  Until the DNS change the next morning, users would still be directed to the SSO login so they'd still be able to login.  Roughly what time would you plan to do it?

I've just noticed that Monday is a bank holiday, but that's OK - just need to make sure I remember to do it. Maybe late afternoon rather than evening.

@louisesimon sorry, not a bank holiday! I'm actually off on my own holiday.
I will do it early Tuesday then. There's still no timing dependency on Innovative's work.

Hi @tomcrane .  No problem!  Enjoy your day off.  Yes, Tuesday morning for deploying this is fine.  Please let me know when done.
The change is going before CAB this morning.  I'll confirm outcome later.

All -the change has been approved so all systems go for Tuesday 19th!
I'll shortly add here the latest (final?) version of the task list for go live.

@tomcrane @jennpb, all - here is the list of task to make the changes live tomorrow.  Please let me know if any questions
GO LIVE tasks 19th May.docx

Good morning all,
I have completed the anonymising process on wellcomelibrary.org.
This includes a redirect for all paths under what was the bookmarks/account page, so they get redirected to the new remnant page, e.g., http://wellcomelibrary.org/account/beeswax.
At time of writing, the DDS can still make direct contact with the Sierra patron info service. This means it can authenticate the user, and provide the user's permissions to the DLCS so that the DLCS can authorise access to clinical and restricted images as appropriate.
For example, here is a clinical video that will present the new login page with @jennpb's edits:
https://wellcomelibrary.org/item/b17478613
And this is a test b number for a clinical book.
https://wellcomelibrary.org/item/b17478613
Further edits to that login page can be made in GitHub, and edits to the account page can be made in the Smart Client.
See how the labels and messaging feels on the now-live site. We can easily change the links in the top right if they don't seem right.
It all seems to have gone very smoothly. The Sierra login is still directing to CAS SSO right now, but that will change as III do their bits.
Once we are happy with all this, the one remaining task from my point of view is the second bullet here - https://github.com/wellcomecollection/platform/issues/4016#issuecomment-627217951 - which is for Wellcome to do.

The Clinical login panel gives incorrect information - I hadn't clocked that UV logins would also need to change. Can you please direct me to where I can edit those modals?

From: Tom Crane<EMAIL_ADDRESS>Sent: 19 May 2020 09:30
To: wellcomecollection/platform<EMAIL_ADDRESS>Cc: Jennifer Phillips-Bacher<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [wellcomecollection/platform] Library site CAS SSO decommisioning (#4016)
Good morning all,
I have completed the anonymising process on wellcomelibrary.org.
This includes a redirect for all paths under what was the bookmarks/account page, so they get redirected to the new remnant page, e.g., http://wellcomelibrary.org/account/beeswaxhttps://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwellcomelibrary.org%2Faccount%2Fbeeswax&data=02|01|j.phillips-bacher%40wellcome.ac.uk|11a8a27076cd4c80b17f08d7fbcef156|3b7a675a1fc84983a100cc52b7647737|0|0|637254739978288827&sdata=L83%2BOXsPrINoa%2BgNUpiAZLXB9EZr%2BGuSEQ1cdB3OSXY%3D&reserved=0.
At time of writing, the DDS can still make direct contact with the Sierra patron info service. This means it can authenticate the user, and provide the user's permissions to the DLCS so that the DLCS can authorise access to clinical and restricted images as appropriate.
For example, here is a clinical video that will present the new login page with @jennpbhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjennpb&data=02|01|j.phillips-bacher%40wellcome.ac.uk|11a8a27076cd4c80b17f08d7fbcef156|3b7a675a1fc84983a100cc52b7647737|0|0|637254739978298822&sdata=t8kgWqJbPxLgnXrcKZXN%2BwIT6a8ua9FpSK6VRcj9J9w%3D&reserved=0's edits:
https://wellcomelibrary.org/item/b17478613https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwellcomelibrary.org%2Fitem%2Fb17478613&data=02|01|j.phillips-bacher%40wellcome.ac.uk|11a8a27076cd4c80b17f08d7fbcef156|3b7a675a1fc84983a100cc52b7647737|0|0|637254739978298822&sdata=wx%2BdZ8MaY2ea4sHLMoLmApPyzKWoYxdQ%2BWcrwmoExWg%3D&reserved=0
And this is a test b number for a clinical book.
https://wellcomelibrary.org/item/b17478613https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwellcomelibrary.org%2Fitem%2Fb17478613&data=02|01|j.phillips-bacher%40wellcome.ac.uk|11a8a27076cd4c80b17f08d7fbcef156|3b7a675a1fc84983a100cc52b7647737|0|0|637254739978308813&sdata=hKyr38RES%2BXrU3eMjNRIeITo1LO%2FM2sGV%2FoFyosq%2B6o%3D&reserved=0
Further edits to that login page can be made in GitHub, and edits to the account page can be made in the Smart Client.
See how the labels and messaging feels on the now-live site. We can easily change the links in the top right if they don't seem right.
It all seems to have gone very smoothly. The Sierra login is still directing to CAS SSO right now, but that will change as III do their bits.
Once we are happy with all this, the one remaining task from my point of view is the second bullet here - #4016 (comment)https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fwellcomecollection%2Fplatform%2Fissues%2F4016%23issuecomment-627217951&data=02|01|j.phillips-bacher%40wellcome.ac.uk|11a8a27076cd4c80b17f08d7fbcef156|3b7a675a1fc84983a100cc52b7647737|0|0|637254739978308813&sdata=3eyxgclSEzg51atX12OqrEkM616KvcrlP9yQ675tOcI%3D&reserved=0 - which is for Wellcome to do.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fwellcomecollection%2Fplatform%2Fissues%2F4016%23issuecomment-630670353&data=02|01|j.phillips-bacher%40wellcome.ac.uk|11a8a27076cd4c80b17f08d7fbcef156|3b7a675a1fc84983a100cc52b7647737|0|0|637254739978318809&sdata=QglmLYr8NVD6rdQBgJt8OGve1fRDqL0NRsH8SXZV4L0%3D&reserved=0, or unsubscribehttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAALBB62A7MNAA6ZHVRLYR5TRSI7TXANCNFSM4JHLWY3Q&data=02|01|j.phillips-bacher%40wellcome.ac.uk|11a8a27076cd4c80b17f08d7fbcef156|3b7a675a1fc84983a100cc52b7647737|0|0|637254739978318809&sdata=pqmV4mOKckm5kBFUACLtPLbvZU1cfQmDXHyVgkgBEEU%3D&reserved=0.

Thanks, Tom, Jenn.
D&T have made the DNS change.
I've made live the webpac changes to the Library account page.  (Bookmark link on LHS of login screen is still displaying even though it's been removed from the page  Will wait until III have finished their work and take up with III if still a problem then.)

I've made the changes to the three pages in CM7. All links now go to the correct page.

III have finished their configuration.
Please can you test http://catalogue.wellcomelibrary.org/patroninfo.  We have noticed that Global Protect is still directing this to the account.wellcome.ac.uk.  If you turn GP off or login from a non-work device, it directs to the Sierra login.
However, after logging in , if I go to other Library website pages and then back to 'My Library Account', it needs to login again.  @tomcrane presume this is one for III?

Hi @louisesimon - the direct link to /patroninfo wouldn't trigger a new login if you were already logged in over there, when I tested this on the previous setup. In Sierra, it redirected to your patron details. So I think one for III.
If that fixed link from wl.org should go somewhere else let me know, it's easily changed.

hi all
Staff can now login from a work laptop (there was an internal DNS change that had to be made too).
The remaining issues are:

Encore search still http.  This morning Phil Hunt, the IIIengineer, apologised and said that we we would have to upgrade to encore 4.7.3 to get search as https.  I've queried this with him as before the SSO reinstall last year, our Encore search was https:// and that was an older version of Encore.
I was given to understand that once SSO was removed, the workaround that redirected Encore to http after the SSO resinstall could be removed.

The problems we have with our WAM proxy links remain.  Will continue that with III off this thread.

The 'My Library Account'  login link on the library home page - if you click back on it after logging in, you are directed back to the login page.  No problem when going to an 'embedded' My library account page via Encore or webpac.

I'll look more at this with III. It may be that it's less confusong for users not to have that login button there at all.
Let me know if any questions.
Thanks
Louise

Hi all
Update:
1)Encore search and display is now https.  However, the browsers still show a full record display as insecure because there is an http bit of hardcoded content it is loading (a google book preview link).
2) WAM proxy links now working.
3) @tomcrane Please can you remove the final '/' from the /patroninfo link on the 'My Library Account' page.  It probably won't make a difference, but would be good to check.
Thanks
Louise

Hi @tomcrane
I think you mentioned you did some work on the image links from the library catalogue to WC.org.
Staff report that the image link is broken.  e.g. clicking on the image link in https://search.wellcomelibrary.org/iii/encore/record/C__Rb1569989?lang=eng
Is this one for you ?
Thanks
Louise

Hi @louisesimon
Not one for me I'm afraid.
This link:
http://catalogue.wellcomelibrary.org/search~S8?/.b1569989/.b1569989/1,1,1,B/l962~b1569989&FF=&1,0,,0,0
...gets redirected to...
http://wellcomeimages.org/indexplus/image/V0008852.html
which then gets redirected to...
https://wellcomecollection.org/works?query=V0008852&wellcomeImagesUrl=/indexplus/image/V0008852.html
...which doesn't find anything. I don't know where in the chain the problem lies, but none of the links in the chain are things I know about, sorry!

On the other issue...
with or without the /, going straight to /patroninfo now triggers a logout from Sierra.
I also tried https://catalogue.wellcomelibrary.org/patroninfo~S8/

On the other issue...
with or without the /, going straight to /patroninfo now triggers a logout from Sierra.
I also tried https://catalogue.wellcomelibrary.org/patroninfo~S8/

Thanks, Tom.  We'll see how it goes.  I'll talk to the library engagement team about user feedback.  If it proves too confusing, then we may have to remove the link and offer just the login on Encore and webpac pages.
@jennpb  - is that okay with you

Re https://github.com/wellcomecollection/platform/issues/4016#issuecomment-631957505
James Gorrie might know about the redirects from Encore to wc.org. I'll ask him

@louisesimon Fine with me, whatever works.

Update.  As of yesterday, Encore searches and results are no longer getting a browser warning that the page is insecure.  Http content loading on the page has been identified and changed to https or removed.   For info, the exception to this are records with old wellcome images http URls in them.
The only other thing to test is restricted content.  I'll do that once I've identified a restricted content record.

Hi @tomcrane
Please can you change the email contact on  https://wellcomelibrary.org/account from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>.  This ensures it tallies with the email message sent out to Bookmarks users before the feature was turned off.
Thanks
Louise

And for @louisesimon -
This is not absolutely time critical but can happen soon after the changes above.

I will add a rule to the wl.org estate that redirects any sub path of wellcomelibrary.org/account back up to wellcomelibrary.org/account. This handles any direct links to bookmarks that people might have made (rather than them seeing a 404 page).
???* will change the routing for account.wellcome.ac.uk so that all requests for that hostname (whatever the path) will be redirected to wellcomelibrary.org/account. This explains what just happened if there are bookmarks or any other links hanging about that go to the SSO site.

The latter redirect shouldn't happen within the account.wellcome.ac.uk estate because we want to switch all that off. It should happen at the load balancer, I suppose.
*sorry for the ???, don't know who will do this bit.

@tomcrane Just been speaking to Dan Murarasu about the above.  They want to make things as uncomplicated as possible and have asked if it's okay to just have account.wellcome.ac.uk reroute to the Wellcome Library IP address. ie anyone who has account.wellcome.ac.uk bookmarked will get rerouted to Wellcome Library home page.  OK with you?

We can still achieve the original suggestion in this scenario. If account.wellcome.ac.uk resolves to the wellcomelibrary.org load balancer, then as long as I can see the original request host name when the request arrives at the DMZ servers, I can add a rule that says:

if the host name is account.wellcome.ac.uk, then whatever the path, send a redirect to wellcomelibrary.org/account

I can see other hostnames that terminate here, e.g., library.wellcome.ac.uk is redirected in the same way.

Thanks, Tom.  OK if Dan contacts you direct via Slack on this?

Yes!

Please can you change the email contact on https://wellcomelibrary.org/account from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>
I made this change in CM7

Thanks, Jenn.
Louise
From: jennpb<EMAIL_ADDRESS>Sent: 28 May 2020 09:05
To: wellcomecollection/platform<EMAIL_ADDRESS>Cc: Louise Simon<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [wellcomecollection/platform] Library site CAS SSO decommisioning (#4016)
Please can you change the email contact on https://wellcomelibrary.org/accounthttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwellcomelibrary.org%2Faccount&data=02|01|l.simon%40wellcome.ac.uk|1bf7412fb4974be70f7e08d802ddd221|3b7a675a1fc84983a100cc52b7647737|0|0|637262499020629454&sdata=Gav5YYXPgNWtz%2BaNqTSXHu73yyXEIWa0B%2B9DNCnj%2BAs%3D&reserved=0 from digital<EMAIL_ADDRESS>to library<EMAIL_ADDRESS>I made this change in CM7
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fwellcomecollection%2Fplatform%2Fissues%2F4016%23issuecomment-635185025&data=02|01|l.simon%40wellcome.ac.uk|1bf7412fb4974be70f7e08d802ddd221|3b7a675a1fc84983a100cc52b7647737|0|0|637262499020629454&sdata=Jl0IH2H%2BnW%2B%2BzPNx%2FxM5uXCNA89CNQQ12koSPgEtvGE%3D&reserved=0, or unsubscribehttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAMOSFLZLTE7UXGEBSRPADLRTYLKXANCNFSM4JHLWY3Q&data=02|01|l.simon%40wellcome.ac.uk|1bf7412fb4974be70f7e08d802ddd221|3b7a675a1fc84983a100cc52b7647737|0|0|637262499020629454&sdata=jah7PutswSAVsxwqKHMf0Frtumc2IDB%2BdrTQd2rUIUk%3D&reserved=0.


Can't use db:create with postgres

Just installed postgres with default settings. Created this config:
{
  "defaultEnv": "local",
  "local": {
    "driver": "pg",
    "user": "postgres",
    "password": [my password],
    "host": "localhost",
    "database": "identity",
    "schema": "public"
  }
}

Then tried running

db-migrate db:create identity

.
Got error:

[INFO] Detected and using the projects local version of db-migrate. 'D:\Development\friendswithgoals\databases\identity\node_modules\db-migrate\index.js'
[INFO] Using local settings: { driver: 'pg',
user: 'postgres',
password: '******',
host: 'localhost',
database: 'identity',
schema: 'public' }
[INFO] require: db-migrate-pg
[INFO] connecting
[INFO] connected
[SQL] CREATE DATABASE "identity"
[ERROR] error: database "identity" does not exist
at Connection.parseE (D:\Development\friendswithgoals\databases\identity\node_modules\db-migrate-pg\node_modules\pg\lib\connection.js:539:11)
at Connection.parseMessage (D:\Development\friendswithgoals\databases\identity\node_modules\db-migrate-pg\node_modules\pg\lib\connection.js:366:17)
at Socket. (D:\Development\friendswithgoals\databases\identity\node_modules\db-migrate-pg\node_modules\pg\lib\connection.js:105:22)
at emitOne (events.js:77:13)
at Socket.emit (events.js:169:7)
at readableAddChunk (_stream_readable.js:153:18)
at Socket.Readable.push (_stream_readable.js:111:10)
at TCP.onread (net.js:531:20)

Tried taking out "database" "identity" from config, and got:

[INFO] Detected and using the projects local version of db-migrate. 'D:\Development\friendswithgoals\databases\identity\node_modules\db-migrate\index.js'
[INFO] Using local settings: { driver: 'pg',
user: 'postgres',
password: '******',
host: 'localhost',
schema: 'public' }
[INFO] require: db-migrate-pg
[INFO] connecting
[INFO] connected
[SQL] CREATE DATABASE "identity"
[ERROR] error: database "savel" does not exist
at Connection.parseE (D:\Development\friendswithgoals\databases\identity\node_modules\db-migrate-pg\node_modules\pg\lib\connection.js:539:11)
at Connection.parseMessage (D:\Development\friendswithgoals\databases\identity\node_modules\db-migrate-pg\node_modules\pg\lib\connection.js:366:17)
at Socket. (D:\Development\friendswithgoals\databases\identity\node_modules\db-migrate-pg\node_modules\pg\lib\connection.js:105:22)
at emitOne (events.js:77:13)
at Socket.emit (events.js:169:7)
at readableAddChunk (_stream_readable.js:153:18)
at Socket.Readable.push (_stream_readable.js:111:10)
at TCP.onread (net.js:531:20)

Migrations seem to be working fine. I was able to manually create db, and run migrations. Just wondering what I'm doing wrong here.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/36348106-can-t-use-db-create-with-postgres?utm_campaign=plugin&utm_content=tracker%2F73887&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F73887&utm_medium=issues&utm_source=github).

Duplicate of #338
The problem is, that db-migrate does try to connect to the database of your configuration, which will result in the error you have seen. database less connections are one of our work items though.

Hey, thanks for the quick response! If I take the database and schema out of the configuration, should it work?

Depends on the driver actually, either you need to define one that already exists or just no db at all.
In case of pg we just pass the config to the pg driver below:
https://github.com/db-migrate/pg/blob/master/index.js#L494
In the case of pg this means it defaults to the username of the user executing db-migrate:
https://github.com/brianc/node-postgres/wiki/Client#new-clientobject-config--client
Thus probably it might not help to remove this setting and I'm not sure if an empty string database setting would help.
So probably we need to switch over to use https://github.com/brianc/node-postgres/wiki/Connection instead  though.

For anyone who runs into this, my workaround was to create a separate database_create.json configuration file that looks like this (without a database property):
{
  "defaultEnv": "local",
  "local": {
    "driver": "pg",
    "user": "postgres",
    "password": [my password],
    "host": "localhost",
    "schema": "public"
  }
}

I then run the create command like this:
node_modules/db-migrate/bin/db-migrate --config database_create.json db:create identity

Just a heads up that using the above approach can be automated using jq, rather than creating two separate config files:
jq 'del(.mysql.database)' database.json > ./database-without-key.json &&\
db-migrate --config ./database-without-key.json -e mysql db:create alcomixer &&\
rm ./database-without-key.json


KeepKey Settings: Passphrase update success message displayed by default

Overview
The passphrase screen in KeepKey Settings shows "Passphrase successfully updated!" before clicking anything.
References and additional details
(tbd)
Acceptance Criteria

The confirmation message should only display on an actual update of the passphrase, not by default.

Need By Date
No response
Screenshots/Mockups

Estimated effort
2 hours

... dangit, this was on a feature branch. sorry for the confusion.

Yes ser, that was a bug that I believe I fixed before the feature was rolled out 👍


When the custom formatter displays computed, it will display undefined, which is inconsistent with the actual situation.

Vue version
3.5.13
Link to minimal reproduction
https://play.vuejs.org/#eNp9UE1Lw0AQ/SvLXtpCSJHgpbQFLRX0oKIeFySkk7h1v9idrYWS/+7shtQepLeZ997MvHknfudceYjAF3wZGi8dsgAY3VoYqZ31yE7MQ1swaSRuYkCrH6zXNSL4orHaRYQd61nrrWYTWjQRRpjGmoCsZis2SqbT2Wrd1irAbBRYBaWy3bTOyHI+nKfD1CBop2oE6pbzi4YXHAMNt7Ir98Easn0ShjHB0yGpwL84lLRc8AXLTOJqpezPU8bQRyhGvPmC5vsffB+OCRP81UMAfwDBzxzWvgMc6O37MxypPpPa7qIi9RXyDejxmDwOsvtodmT7QpfdPubwpek+wvaIYML4VDKalH3WC06Rb668/me3Kqs8J0xPKX4ewKedFGBV3pY3Fe9/AQ4urzs=
Steps to reproduce

open chrome devtools custom formatter;
view console;

What is expected?
Display the correct value
What is actually happening?
display undefined
System Info
No response
Any additional comments?
No response

I think it should be modified like this, but I don't know if it is correct?

I think it's as expected, there is a lazy feature in the computed attribute that calculates the value only when accessed, and this lazy calculation shouldn't be triggered in the custom formatter, so the displayed value is always undefined
playground

It's weird, because edge shows

@Bayn-Web
You should first enable Custom formatters.

I agree with @yangxiuxiu1115, this is the expected behavior.


Couldn't find file 'gmaps/google' with type 'application/javascript'

Rails beginner.
I have followed step-by-step the Requirements page (added gem into Gemfile, bundle install, added div, added javascript dependencies and source code with asset pipeline and finally added the javascript inside view) but, when I load my homepage I get the following:
couldn't find file 'gmaps/google' with type 'application/javascript'
I have googled something and finally I have tried to remove the 2 following lines inside application.html.erb:
<%= stylesheet_link_tag 'application', media: 'all', 'data-turbolinks-track': 'reload' %> <%= javascript_include_tag 'application', 'data-turbolinks-track': 'reload' %>
Doing this I got the trick and the homepage is correctly loaded.

Maybe my mistake in adding and installing the gem


Support Java code release?

Could you expand? What kind of Java code? What does a release look like? Does it involve compiling a war file and uploading to Tomcat?

Yes, we need to compile Java code war and jar, and upload it to Tomcat.

To my knowledge there isn't an off-the-shelf plugin for Capistrano that does that sort of WAR/JAR deployment to Tomcat. You might check Stack Overflow to see if anyone has attempted it and is willing to share.
Unless you are already invested in Capistrano, I recommend not using Capistrano for this particular scenario. It sounds like you want to build a WAR/JAR locally and then upload it. That goes against the grain of Capistrano's standard deployment flow, which is to export files directly from a source code repository to the server.
--
GitHub issues are for feature requests or bug reports. Since this is more of a how-to question, I am closing this issue. The Capistrano team recommends you use Stack Overflow for general questions. For more details, please see our contribution policy.

Okay, thank you for your patience to answer, publishing tools or other code, thank you very much


support for the current v2 api of rpine pallete

support for the current v2 api of rpine pallete

Waiting on official release of rose-pine/palette v2


Add sitemap

Sitemap has been generated 64e9a4f63fc37f576214be8f7aa1d74d82eefac7, although Google is seemingly having problem fetching it. All other tools report it as OK. Got recommendation to simply wait a few days for Google to index all of it.


open links on new tab?

On the profile page, if you go and click a link "View my solution" the link is loaded in the same window (this are external links from codepen.io).

Thanks for pointing this out! This will be fixed in tomorrow's release!


Unclear documentation for sockaddr_storage_to_addr()

In the latest master,  the documentation for sockaddr_storage_to_addr() says:

The len argument should be the number of bytes in the sockaddr_storage that are actually allocated and valid.  It must be at least as large as all the useful parts of the structure.  Note that in the case of a sockaddr_un, len need not include the terminating null.

For a unix sockaddr, the "[The len] must be at least as large as all the useful parts of the structure" makes it sound like the len is allowed to be larger than the useful part of the structure. It's also unclear what "valid" and "useful" mean in this context. For example, it's common for C code to initialize something like sockaddr_un { family: AF_UNIX, path: b"tmp.sock\0" }, but use a length of size_of(sockaddr_un) when passed to syscalls. But sockaddr_storage_to_addr() calls from_raw_parts() which has the documentation:

sun_len is the size of the valid portion of the struct, excluding any trailing NUL

So the len argument to sockaddr_storage_to_addr() must not be larger than offsetof(addr.path) + strlen(addr.path) for pathname unix sockaddrs.
This issue causes a panic in the latest nix release (0.23.1) due to https://github.com/nix-rust/nix/blob/afba7c5a33dd4fd62b047e64089487cf822ccec2/src/sys/socket/addr.rs#L619-L622

How about this wording?
For fixed size sockaddr types, the `len` should be the size of the concrete sockaddr type (e.g. `sockaddr_in`).
In the case of `sockaddr_un`, it should be the length of the structure up to but not including the trailing NUL.

However, note that this function will be deprecated in the next release of Nix.  Its replacement has not yet been committed to the master branch, but its signature will be similar.


Sprt

fixes for mSPRT method

🚀 Deployed on https://67240eae8243cc67f1fea6f1--cozy-fox-0defec.netlify.app


[Question]: Ragflow Compatibility with Docker on Windows and Adjusting vm.max_map_count

Describe your problem
Dear Ragflow team,
I’m working on a project involving Ragflow and I have a couple of questions regarding its compatibility with Docker on a Windows environment.
1.Compatibility with Docker on Windows:

If I decide to deploy Ragflow on Windows using Docker build, is it compatible to do so?

2.Adjusting vm.max_map_count on Windows:

In addition, how to adjust max_map_count if I'm not using WSL.

Any insights or additional documentation you can provide would be greatly appreciated. Thank you!

Yes
·vm.max_map_count is for Linux. If you run Ragflow on Docker for Windows successfully, then you can ignore it. If elasticsearch can't be started, you can edit your .wslconfig file to allocate more resources (especially memory) for Docker (assuming you use WSL2 rather than hyper-v as Docker's backend engine).

I've used the solution from here: https://stackoverflow.com/questions/42111566/elasticsearch-in-windows-docker-image-vm-max-map-count
And it started without any problems.

I have been stuck for months on this problem, the solution is launch the following commands on cmd.exe (try Powershell or Bash if cmd doesn't work), as stated in the official Elasticsearch documentation:

wsl -d docker-desktop
sysctl -w vm.max_map_count=262144
And you are ready to start Elasticsearch!


Occur error on env of immediately after the restart

Occur error on docker-machine env of immediately after the docker-machine restart

e.g.
$ docker-machine restart test-xhyve; docker-machine env test-xhyve

Result,
> Reading CA certificate from /Users/zchee/.docker/machine/certs/ca.pem
> Reading server certificate from /Users/zchee/.docker/machine/machines/test-xhyve/server.pem
> Reading server key from /Users/zchee/.docker/machine/machines/test-xhyve/server-key.pem
> Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "<IP_ADDRESS>:2376": dial tcp <IP_ADDRESS>:2376: getsockopt: connection refused
> You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
> Be advised that this will trigger a Docker daemon restart which will stop running containers.

but, wait for 5sec, succeeded env


x/crypto/pbkdf2: move to standard library

For archive/zip to support reading/writing encrypted volumes (see #12081) it needs pbkdf2 to derive encryption and authentication keys from a password. The package x/crypto/pbkdf2 would need to be moved into the standard library.

Perhaps it's better to have a x/exp/archive/zip (or x/compress/archive/zip
in a new subrepo) for handling encrypted zip files.

Another possibility is to vendor the pbkdf2 package similar to how hpack is currently done.

It is a small package so moving to /internal or straight copying over works.

I don't see this being moved to the standard library just to enable encrypted archives support in archive/zip; vendoring (or just the copy-pasting the needed functionalities) seem more likely; this can be done as a part of the work for #12081 (archive/zip: support for encrypted archives) and it can be tracked there, so I think we can safely close this issue.


core.stdc.stdio: prepare for MSVCRT 2014 support

Once MSVC 2014 is required, things will get easier, for example here because they now provide a standard-conformant (v)snprintf() implementation (except for x87 support), see this MSDN blog.
Additionally, _fputc_nolock() and _fgetc_nolock() are no longer defined as macros, but available in the library, just like any other supported C runtime.

This should be using a separate version statement for the 2014 version. There is no reason that earlier versions should be prevented from building DMD and D code.

The 2014 version (well, so much time has passed for such a mini-PR, that the VS version has been advanced to 2015 in the meantime :o)) is disabled and only there to urge the responsible people to move on with Windows and MSVCRT support.
Once enabled, it may break code iff that code was written explicitly for MSVCRT, i.e., using the non-standard old modifiers. And imo that's highly unlikely, given the current MSVCRT support. :]

The last commit is by no means complete.
What would be needed is something very similar to https://github.com/kinke/druntime/commit/3c897cfc86c696e5a28f716b7a03fcb28a111950.
Given that there's absoletely no progress regarding my DMD PRs, I'll focus on LDC only in the future, where contribution is still appreciated.


Android build failed

I am trying to build the app, but it fails. I am on release/1.3.0 and I am using fvm.
This is the error:
1: Task failed with an exception.

What went wrong:
Execution failed for task ':device_info_plus:compileDebugJavaWithJavac'.

Could not resolve all files for configuration ':device_info_plus:androidJdkImage'.
Failed to transform core-for-system-modules.jar to match attributes {artifactType=_internal_android_jdk_image, org.gradle.libraryelements=jar, org.gradle.usage=java-runtime}.
Execution failed for JdkImageTransform: /Users/tomislavgrdenic/Library/Android/sdk/platforms/android-34/core-for-system-modules.jar.
Error while executing process /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/jlink with arguments {--module-path /Users/tomislavgrdenic/.gradle/caches/transforms-3/c66d6905e9178766417c242e6b14a315/transformed/output/temp/jmod --add-modules java.base --output /Users/tomislavgrdenic/.gradle/caches/transforms-3/c66d6905e9178766417c242e6b14a315/transformed/output/jdkImage --disable-plugin system-modules}

This is the output of flutter doctor -v:
[✓] Flutter (Channel stable, 3.22.2, on macOS 13.5.1 22G90 darwin-arm64, locale
en-HR)
• Flutter version 3.22.2 on channel stable at
/Users/tomislavgrdenic/fvm/versions/3.22.2
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 761747bfc5 (4 months ago), 2024-06-05 22:15:13 +0200
• Engine revision edd8546116
• Dart version 3.4.3
• DevTools version 2.34.3
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
• Android SDK at /Users/tomislavgrdenic/Library/Android/sdk
• Platform android-34, build-tools 34.0.0
• ANDROID_SDK_ROOT = /Users/tomislavgrdenic/Library/Android/sdk
• Java binary at: /Applications/Android
Studio.app/Contents/jbr/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 21.0.3+-79915917-b509.11)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 15.2)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 15C500b
• CocoaPods version 1.13.0
[✗] Chrome - develop for the web (Cannot find Chrome executable at
/Applications/Google Chrome.app/Contents/MacOS/Google Chrome)
! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[✓] Android Studio (version 2024.2)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 21.0.3+-79915917-b509.11)
[✓] VS Code (version 1.94.0)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.99.20240930
[✓] Connected device (3 available)
• AC2003 (mobile)                 • 17e83838              • android-arm64 • Android 12 (API 31)
• macOS (desktop)                 • macos                 • darwin-arm64  • macOS 13.5.1 22G90 darwin-arm64
• Mac Designed for iPad (desktop) • mac-designed-for-ipad • darwin        • macOS 13.5.1 22G90 darwin-arm64
! Error: Browsing on the local area network for Team’s iPad. Ensure the device is unlocked and attached with a cable or associated with the same local area network as this Mac.
The device must be opted into Developer Mode to connect wirelessly. (code -27)
[✓] Network resources
• All expected network resources are available.

Hello,
Never seen this error before. I've googled it a bit and seems it might be connected with a java version.
I see you have
Java version OpenJDK Runtime Environment (build 21.0.3+-79915917-b509.11)
but my is
Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)
Could you try to decrease your java version to see if will it help?

Hi, and thanks.
I downgraded java to 17.0.9 and I finally built the app.


How to  accelerate use jit in loop

In my situation , i want use jit to compile the function once , and the big numpy array can be compile in the jit . but  in next loop the big numpy array will be change to another numpy array
from numpy import random
from jax.numpy import sqrt, pi, exp, log
import matplotlib.pyplot as plt
from jax import jit, grad
import iminuit
from iminuit.util import make_func_code, describe
sigma = 5.0
mu = 100.0
N = 100
tries = 2
s0 = sigma + random.randn(tries) * 0.5
s1 = mu + random.randn(tries) * 10.0
def _Likelihood(s, m, w):
    sum = 0
    for _x in w:
        term = -log(1 / (s * sqrt(2. * pi)) * exp(- ((_x - m) / s)**2 / 2.))
        sum += term
    return sum

def Likelihood(pars):
    return jit(_Likelihood)(pars[0], pars[1], x)

def my_dev_likelihood(pars):
    return jit(grad(_Likelihood))(pars[0], pars[1], x)

for ss, mm in zip(s0, s1):
    x = random.randn(N) * sigma + mu
    my_pars1 = (ss, mm)
    my_pars2 = (ss+0.1, mm+0.1)
    my_dev_likelihood(my_pars1)
    my_dev_likelihood(my_pars2)

in my code ,  i find that it is updata the x each loop in my_dev_likelihood , but the jit can not accelerate because x is a parameter , and x calculate in each loop in each  my_dev_likelihood . so i want some method that make the first  my_dev_likelihood the x is a const in function and be compile and in second my_dev_likelihood it will be fast ,and  in next loop the x will updata and creat new graph

I am having a hard time understanding your description of the problem. One thing that would help would be to reduce the code to a minimum (one function with one loop and jit, and explaining which function call you expected to run faster.
I see two loops in your code. The for loop inside _Likelihood is not compiled as a loop but is unrolled. I assume you have seen this. I suspect that you are talking about the second loop, which changes x, even though x is not an argument to the function. It is true that since x is not an argument, the first time the loop is compiled the value of x is stored in the compiled code. (That situation is also described in the Pure Functions part of the above notebook.)
You must pass x to the _Likelihood function.


Remove Any Module Replace Directives

Please describe the problem you have
If go.mod includes any replace directives, remove them before cutting a release.

Closing issue since no replace directives currently exist and we have no plans to add any.


Error when taking up previously created cluster

./oc-cluster up foo ./oc-cluster down ./oc-cluster up foo
Give me the following error message
[INFO] Running a previously created cluster
oc cluster up --public-hostname <IP_ADDRESS>                 --host-data-dir /Users/bjartek/.oc/profiles/foo/data                 --host-config-dir /Users/bjartek/.oc/profiles/foo/config                 --routing-suffix                  --use-existing-config
-- Checking OpenShift client ... OK
-- Checking Docker client ... OK
-- Checking Docker version ... OK
-- Checking for existing OpenShift container ... OK
-- Checking for openshift/origin:v1.3.0 image ... OK
-- Checking Docker daemon configuration ... OK
-- Checking for available ports ... OK
-- Checking type of volume mount ...
Using Docker shared volumes for OpenShift volumes
-- Creating host directories ... OK
-- Finding server IP ...
Using public hostname IP <IP_ADDRESS> as the host IP
Using <IP_ADDRESS> as the server IP
-- Starting OpenShift container ...
Creating initial OpenShift configuration
Starting OpenShift using container 'origin'
FAIL
Error: could not start OpenShift container "origin"
Details:
Last 10 lines of "origin" container log:
W1007 17:17:27.162504   24876 start_master.go:272] Warning: assetConfig.loggingPublicURL: Invalid value: "": required to view aggregated container logs in the console, master start will continue.
W1007 17:17:27.162600   24876 start_master.go:272] Warning: assetConfig.metricsPublicURL: Invalid value: "": required to view cluster metrics in the console, master start will continue.
error: Invalid MasterConfig /var/lib/origin/openshift.local.config/master/master-config.yaml
routingConfig.subdomain: Invalid value: "--use-existing-config": must be a valid subdomain
I get the same result of i source the run file in to foo profiles directory.
I am on a mac using
docker for mac
1.12.1 b1233
oc from homebrew
oc v1.3.0
kubernetes v1.3.0+52492b4

This was fixed in a commit earlier today. I did not use the latest version from the repo. closing.


Building against 0.5.x

Going to land as current build is against a snapshot and not working, and this PR is blocked on issues with streams and subscriptions that will need fixes in reactivesocket-java