You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ctakes.apache.org by "Peter Abramowitsch (Jira)" <ji...@apache.org> on 2020/12/30 16:40:00 UTC

[jira] [Commented] (CTAKES-547) UMLS change in authentication process

    [ https://issues.apache.org/jira/browse/CTAKES-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17256601#comment-17256601 ] 

Peter Abramowitsch commented on CTAKES-547:
-------------------------------------------

DUPLICATE:    I fixed this and checked in new Umls Authentication code.  

See Ctakes Jira CT-545 UMLS Authentication

> UMLS change in authentication process
> -------------------------------------
>
>                 Key: CTAKES-547
>                 URL: https://issues.apache.org/jira/browse/CTAKES-547
>             Project: cTAKES
>          Issue Type: Improvement
>          Components: ctakes-clinical-pipeline
>            Reporter: Akash Indani
>            Priority: Major
>
> Hi Team,
> UMLS has changed the authentication process by identity providers like Google, Microsoft, etc. After Jan 15 there would not be any username and password login available. Although there is another option wherein they are providing the API-key for each user which I think can be used for calling any UMLS APIs. Please have a look at it asap, as without UMLS authentication workflows will fail. I have contacted the UMLS team and below was there reply:
> cTakes will need to update to work with our new authentication. In the meantime, you can go here: [https://uts.nlm.nih.gov/uts/forgot/password] and enter your username (****). You will receive an email with a link to reset your password. Copy the temporary password and click the link. Enter your username and the temporary password, and create a new password. Use your username and password with cTakes. Keep in mind that this will only work until Jan. 15 or until cTakes updates its authentication. 
> Regards,
> UMLS Support



--
This message was sent by Atlassian Jira
(v8.3.4#803005)