[FOLIO-2370] dev.folio.org "Enable Okapi Auth Module on tenant" out of date Created: 29/Nov/19  Updated: 03/Jun/20  Resolved: 18/May/20

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Bug Priority: TBD
Reporter: Adam Dickmeiss Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to OKAPI-725 Okapi does not pass tenant header for... Closed
relates to OKAPI-726 Update guide for case when tenant hea... Closed
relates to FOLIO-2379 Remove old dev.folio.org/tutorials/cu... Closed
Sprint:

 Description   

Tod Olson reported that the dev.folio.org tutorial is out of date

https://dev.folio.org/tutorials/curriculum/03-enable-okapi-authentication/

This is what happens now:

curl -i -w '\n' -X GET -H 'X-Okapi-Tenant: testlib' \
    http://localhost:9130/testb
HTTP/1.1 200 OK
X-Okapi-Trace: GET test-auth-3.4.1 http://localhost:9132/testb : 202 580037us
X-Handler-header: OK
transfer-encoding: chunked
X-Okapi-Trace: GET test-basic-1.0.0 http://localhost:9131/testb : 200 42083us
It works

which is not what the tutorial says (401)



 Comments   
Comment by Peter Murray [ 29/Nov/19 ]

David Crossley: Do you think it is time to just take down the tutorial entirely? I regret that we don't have something for bringing on new developers with some of the conceptual aspects of Okapi and Stripes. I'm also not seeing it as a high priority for one of the development teams to devote part of their sprint cycle to creating.

Comment by David Crossley [ 29/Nov/19 ]

Yes Peter, i do agree. It was useful in the early days. We have tried to keep it up-to-date, but it has become potentially misleading.

Comment by David Crossley [ 30/Nov/19 ]

I will add a new Jira ticket on Monday. The website infrastructure to organise and present the tutorial content took a lot of effort to develop. Perhaps now add a basic placeholder.

Tod, thanks for your effort anyway.

Comment by Peter Murray [ 30/Nov/19 ]

Yes, replacing the content of tutorial pages with a message that says the tutorial has been removed (for now) makes sense. We can use issues attached to FOLIO-1348 Closed as holding pen for ideas and updates to the tutorial content until someone has a chance to get back to it.

Comment by Tod Olson [ 30/Nov/19 ]

Given that Okapi has a [guide in the GitHub repo:https://github.com/folio-org/okapi/blob/master/doc/guide.md] that I was unaware of until Adam Dickmeiss mentioned it, maybe at least a message about that. And I could maybe update some of the lessons as I go through, though I will run into code that needs updating and would need to ask questions.

It seems there's still a good bit of work to bootstrap as a new dev, and that has not changed.

For context, my own use case is that I'm trying to get familiar enough that I can make some assessment of what it would take for me to update mod-login-saml (and maybe mod-login) to a more recent RMB, and possibly add some authorization whitelist. As part of that, I would ideally first be able to diagram out relations between these authorization and authentication modules. And also to assess whether this is all a good use of my time. That's why I was turning to the guides. I think that's what we want people in the community to be able to do.

Comment by David Crossley [ 18/May/20 ]

See notes at FOLIO-2379 Closed .

Generated at Thu Feb 08 23:20:10 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.