add asymmetrical connectivity use cases #54
Conversation
|
I wonder if these can or should really be use cases. It would rule out many things:
We are trying to build a deccentralised system of authentication for the open web here. Closed systems will obviously have problems. In the case of X509 it works because the browser ship some Root certificates to all parties (though note the CRL problem) and in closed systems companies have to add extra certificates to each browser that may want to connect, which is very limiting and of course reduces the deployment to only large institutions. |
|
Just to clarify, all Use Cases get added as 'for panel consideration'. I think as we consider them we can arrive at conclusion that we decide not to support some of them. Considerations happen across various issues and pull requests and IMO it helps to have all use cases clearly documented so we can reference them from all issues which we see them affecting. |
UseCases.md
Outdated
| - Alice uses or is developing http://localhost:8080 to view her photos | ||
| - Alice's Identity Provider can't reach Alice's `localhost:8080` | ||
| - Alice's Pod can't reach Alice's `localhost:8080` |
There was a problem hiding this comment.
This one doesn't seem to be as much of a use case as it is something to look out for. Would you like to phrase this as Alice should be able to test things out in a localhost setting?
There was a problem hiding this comment.
it's not just testing or developing. deployment to localhost should be a legitimate scenario. i'll rephrase in more generic terms (not "to view her photos" but "any app").
UseCases.md
Outdated
| - Alice uses https://coolcode.int.enterprise.example to edit code stored in Customer Bob's Pod | ||
| - *CoolCode* is deployed behind Enterprise.Example's company firewall | ||
| - *CoolCode* is proprietary to Enterprise.Example; or | ||
| - *CoolCode* is a commercial product that is deployed on-premises at Enterprise.Example's datacenter | ||
| - Alice's Identity Provider can't reach https://coolcode.int.enterprise.example | ||
| - Customer Bob's Pod can't reach https://coolcode.int.enterprise.example |
There was a problem hiding this comment.
Same thing here. This should be phrased as a use case with a goal that Alice has to accomplish and not just a setup.
There was a problem hiding this comment.
the intent here was to illustrate by example a possible and legitimate configuration of actors that should work, which is how all the other use cases work. i can rephrase this to more explicitly call out the intent to cover the configuration, and then give the example.
There was a problem hiding this comment.
note too that this use case already includes an implicit goal similar to all the other use cases: "Alice uses X to edit code stored in Customer Bob's Pod"
per request from @elf-pavlik