Yes, we do! The entityID used in the examples below is a generic OpenAthens entityID. To generate WAYFless URLs for your users, replace the entityID value in the examples with your own, URL encoded, entityID.
ClinicalKey
ClinicalKey Homepage
https://auth.elsevier.com/ShibAuth/institutionLogin?entityID=https%3A%2F%2Fidp.eduserv.org.uk%2Fopenathens&appReturnURL=https%3A%2F%2Fwww.clinicalkey.com%2F%23!
ClinicalKey Book
https://auth.elsevier.com/ShibAuth/institutionLogin?entityID=https%3A%2F%2Fidp.eduserv.org.uk%2Fopenathens&appReturnURL=https%3A%2F%2Fwww.clinicalkey.com%2F%23!%2Fbrowse%2Fbook%2F3-s2.0-C20161009781
ClinicalKey search results page
https://auth.elsevier.com/ShibAuth/institutionLogin?entityID=https%3A%2F%2Fidp.eduserv.org.uk%2Fopenathens&appReturnURL=https%3A%2F%2Fwww.clinicalkey.com%2F%23!%2Fsearch%2Fwaterbirth
ClinicalKey Student Homepage
https://auth.elsevier.com/ShibAuth/institutionLogin?entityID=https%3A%2F%2Fidp.elsevier.com%2Fopenathens&appReturnURL=https%3A%2F%2Fwww.clinicalkey.com%2Fstudent%2Fshibboleth
Embase
Embase Homepage
https://auth.elsevier.com/ShibAuth/institutionLogin?entityID=https%3A%2F%2Fidp.eduserv.org.uk%2Fopenathens&appReturnURL=https%3A%2F%2Fwww.embase.com
Engineering Village
https://auth.elsevier.com/ShibAuth/institutionLogin?entityID=https%3A%2F%2Fidp.eduserv.org.uk%2Fopenathens&appReturnURL=https%3A%2F%2Fwww.engineeringvillage.com%2F
Funding Institutional
https://auth.elsevier.com/ShibAuth/institutionLogin?entityID=https%3A%2F%2Fidp.elsevier.com%2Fopenathens&appReturnURL=https%3A%2F%2Fwww.fundinginstitutional.com%2F
PharmaPendium
PharmaPendium Homepage
https://auth.elsevier.com/ShibAuth/institutionLogin?entityID=https%3A%2F%2Fidp.eduserv.org.uk%2Fopenathens&appReturnURL=https%3A%2F%2Fwww.pharmapendium.com%2F
Quosa
https://auth.elsevier.com/ShibAuth/institutionLogin?entityID=https%3A%2F%2Fidp.eduserv.org.uk%2Fopenathens&appReturnURL=https%3A%2F%2Fexample.quosa.com
The appReturnURL parameter must be your own Quosa domain, URL encoded.
Reaxys
Reaxys Homepage
https://auth.elsevier.com/ShibAuth/institutionLogin?entityID=https%3A%2F%2Fidp.elsevier.com%2Fopenathens&appReturnURL=https%3A%2F%2Fwww.reaxys.com%2Fservices%2Foauth%2Fshibboleth-sso
ScienceDirect
ScienceDirect Homepage
https://auth.elsevier.com/ShibAuth/institutionLogin?entityID=https%3A%2F%2Fidp.eduserv.org.uk%2Fopenathens&appReturnURL=https%3A%2F%2Fwww.sciencedirect.com
ScienceDirect article, based on PII
https://auth.elsevier.com/ShibAuth/institutionLogin?entityID=https%3A%2F%2Fidp.eduserv.org.uk%2Fopenathens&appReturnURL=https%3A%2F%2Fwww.sciencedirect.com%2Fscience%2Farticle%2Fpii%2FS0196885815000378
ScienceDirect journal, based on journal title
https://auth.elsevier.com/ShibAuth/institutionLogin?entityID=https%3A%2F%2Fidp.eduserv.org.uk%2Fopenathens&appReturnURL=https%3A%2F%2Fwww.sciencedirect.com%2Fjournal%2Fphysics-of-the-earth-and-planetary-interiors
A note about ScienceDirect and third parties (such as discovery services and link resolvers). It is possible to generate links to SD articles in many ways. Not all ways will work as a WAYFless URL. A third party service can use any kind of metadata, parameters and functions to generate links - and that's okay. For any of these links to initiate the Shibboleth session, however, the rules are the same - if the final redirect from a 3rd party application generates the correct WAYFless URL, we expect it to work. If the WAYFless URL syntax doesn't look like the one above, then we don't expect it to work.
A note about DOI links. When a WAYFless URL contains a DOI rather than a PII link to ScienceDirect, access won't work. That's because a DOI link isn't a one-step link directly to the publisher; a DOI link is a function that looks up the article metadata at yet another third party database, based on its DOI value, it then finds the desired link to the publisher and it then redirects the user to ScienceDirect (provided the article happens to be on SD). However, during the link lookup at the third party database, the SAML authentication response gets lost. So while a user may land on the expected article page... they will not be signed in. Example of such a WAYFless URL that is not expected to work:
https://auth.elsevier.com/ShibAuth/institutionLogin?entityID=https%3A%2F%2Fidp.eduserv.org.uk%2Fopenathens&appReturnURL=https%3A%2F%2Fdoi.org%2F10.1016%2Fj.epsl.2018.08.040
SciVal
SciVal Homepage
https://auth.elsevier.com/ShibAuth/institutionLogin?entityID=https%3A%2F%2Fidp.eduserv.org.uk%2Fopenathens&appReturnURL=https%3A%2F%2Fwww.scival.com
Scopus
Scopus Homepage
https://auth.elsevier.com/ShibAuth/institutionLogin?entityID=https%3A%2F%2Fidp.eduserv.org.uk%2Fopenathens&appReturnURL=https%3A%2F%2Fwww.scopus.com
Scopus author profile page, based on Author ID
https://auth.elsevier.com/ShibAuth/institutionLogin?entityID=https%3A%2F%2Fidp.eduserv.org.uk%2Fopenathens&appReturnURL=https%3A%2F%2Fwww.scopus.com%2Fauthid%2Fdetail.uri%3FauthorId%3D57203032777