Project

General

Profile

Task #7193

Story #7190: Code review with emphasis on authentication implementation

Review CN service implementation support for token auth

Added by Dave Vieglais over 6 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
d1_cn_service
Target version:
Start date:
2015-06-16
Due date:
% Done:

100%

Milestone:
None
Product Version:
*
Story Points:
Sprint:

History

#1 Updated by Rob Nahf about 6 years ago

  • Status changed from New to In Progress
  • Assignee changed from Chris Jones to Rob Nahf
  • % Done changed from 0 to 30

this might have to be done at the component level: metacat, cn-rest-service (resolve), cn-node-registry, and others?

#2 Updated by Rob Nahf almost 6 years ago

  • Category set to d1_cn_service
  • translation missing: en.field_remaining_hours set to 0.0
  • Status changed from In Progress to Closed
  • % Done changed from 30 to 100

CN-rest switched from using CertificateManager to PortalCertificateManager in April of 2015.

For example:

public void updateNodeCapabilities(MultipartHttpServletRequest fileRequest, HttpServletResponse response, @PathVariable String nodeId) throws InvalidToken, ServiceFailure, InvalidRequest, IdentifierNotUnique, NotAuthorized, NotImplemented, NotFound {
    Session session = PortalCertificateManager.getInstance().getSession(fileRequest);

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)