Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jul 23 07:20
    acoburn commented #86
  • Jul 23 05:14
    matthieubosquet commented #146
  • Jul 23 05:14
    matthieubosquet commented #86
  • Jul 11 10:24
    csarven labeled #182
  • Jul 11 10:21
    bblfish opened #182
  • Jul 02 23:40
    elf-pavlik commented #181
  • Jul 02 22:54
    matthieubosquet commented #181
  • Jul 02 21:42
    acoburn commented #181
  • Jul 02 19:02
    elf-pavlik commented #181
  • Jul 02 17:28
    matthieubosquet edited #181
  • Jul 02 17:26
    matthieubosquet edited #181
  • Jul 02 16:57
    matthieubosquet opened #181
  • Jul 02 10:16

    github-actions[bot] on gh-pages

    deploy: 11cbe3b3c68cddc29a34d2b… (compare)

  • Jul 02 10:15

    acoburn on rs-idp-usage

    (compare)

  • Jul 02 10:15

    acoburn on main

    Fix RS-IdP confusion (#180) Th… (compare)

  • Jul 02 10:15
    acoburn closed #180
  • Jul 02 03:48
    acoburn review_requested #180
  • Jul 02 03:48
    acoburn opened #180
  • Jul 02 03:47

    acoburn on rs-idp-usage

    Fix RS-IdP confusion This segm… (compare)

  • Jun 29 10:07
    bblfish commented #145
elf-pavlik @elf-pavlik about to add something on the agenda
elf Pavlik
@elf-pavlik
q+ re stages
elf-pavlik @elf-pavlik got lost which issue are we discussing
Aaron Coburn
@acoburn
agreed
Can we stay focused on Solid-OIDC in this particular conversation?
No, Solid-OIDC does not use the JWT security vocabulary
Sarven Capadisli
@csarven
q+
elf Pavlik
@elf-pavlik
q+ re overlap
Aaron Coburn
@acoburn
q+
elf Pavlik
@elf-pavlik
q+
q+ re: inline issues
Aaron Coburn
@acoburn
+1 on that suggestion
If the identifying value is of the form user/repo#number, Bikeshed assumes you are referring to GitHub repository, and points the issue at the corresponding issue.
Aaron Coburn
@acoburn
Thanks @csarven
acoburn @acoburn is happy to make adjustments to that PR if there are any issues raised
elf Pavlik
@elf-pavlik
q+ re repo
Aaron Coburn
@acoburn
q+ re repo
elf Pavlik
@elf-pavlik
Determine identifier and title for the solid-oidc spec #116
q+ re: can we PR as git subtree ?
elf Pavlik
@elf-pavlik
elf-pavlik @elf-pavlik will need to leave at the hour end
Aaron Coburn
@acoburn
q+
elf Pavlik
@elf-pavlik
q+
Aaron Coburn
@acoburn
+1 to @elf-pavlik 's suggestion
elf Pavlik
@elf-pavlik
q+ re: more constrained than solid protocol making application/ld+json the default response
q- I will reopen the issue
elf-pavlik @elf-pavlik needs to go
acoburn @acoburn needs to go
elf Pavlik
@elf-pavlik
guys please write down you conclusions in minutes, thank you
Aaron Coburn
@acoburn
@bblfish:matrix.org to be clear, I'm not interesting in removing WebID from Solid-OIDC, I just want to generalize over it. Rather than requiring WebID as the one-and-only way to identify agents, I want WebID to be one-of-many ways to identify agents
Aaron Coburn
@acoburn
@csarven in today's call we discussed adding a solid-oidc repository (presumably under the solid organization). Is this something you can do? I don't have permissions to do this. Thanks!
Sarven Capadisli
@csarven
@acoburn Not sure if we actually agreed to proceed with that but... created https://github.com/solid/solid-oidc . Added you, Pavlik, Dmitri as maintainers.
Aaron Coburn
@acoburn
@csarven thanks! I must have jumped to that conclusion based on a ~2 week timeframe (give or take) for a ~FPWD. Either way, this will help us proceed
Aaron Coburn
@acoburn
@csarven it looks like solid/vocab#51 has been approved. Is there a process for getting that merged and putting those resources online?
Sarven Capadisli
@csarven
Sorry, didn't get to it. Walked through it with Tim and he approved. I was on/off past days.. Merged now. I'll nudge people again to get it up on w3.org
Aaron Coburn
@acoburn
Monday is a holiday in the US, so I'll not make Monday's meeting, but I'll read the notes afterwards
elf Pavlik
@elf-pavlik
I'm also pretty busy today, happy to postpone till next week once we moved forward on github.
Justin Bingham
@justinwb

Hi @/all - given some movement and activity of late related to client/server notification protocols, the protocol editors have created an issue at solid/process#258 to gauge interest in re-establishing the notifications panel to advance proposals and implementation work:

Please see solid/process#258 and :+1: / :-1: / comment if you’re interested in participating.

Thanks @ericprud
Aaron Coburn
@acoburn
I have a meeting conflict today so I will miss this week's authN panel
elf Pavlik
@elf-pavlik
I also didn't get to do my actions. I created pad for next week and put them there to get them done this week. Everyone please add your agenda items for next week
https://hackmd.io/q7imkb2yQjav0NS0GN-9HQ
Aaron Coburn
@acoburn

I have copied the current state of the Solid-OIDC specification and associated primer to the new https://github.com/solid/solid-oidc repository.

New changes should target that repository.

There are a few repository setup details that @csarven or another admin will need to take care of :

  • Delete head branches on merge. This is a setting that can be enabled by an admin (this is a nice-to-have, but I'd appreciate it)
  • Publication of editor's draft. The CI/CD pipeline currently generates HTML files in the gh-pages branch. We should either enable the publication of docs in that location or set up some other mechanism such that one can easily read the specification in an HTML browser
  • Branch protection needs to be set up: prevent any force-pushes, pushes directly to main. Please also gate merges on the successful passing of the CI tasks
  • I don't believe we need wikis and projects enabled on the repository
Aaron Coburn
@acoburn
No one else was present for the authN panel meeting, so let's take up these topics next week
elf Pavlik
@elf-pavlik
I'm sorry for not making it to the call yesterday. This week I will follow up on some issues via github.
Sarven Capadisli
@csarven
@acoburn I've updated the settings.
elf Pavlik
@elf-pavlik
Today I'm available to join the call. To stay honest I'm still caught up in implementing Solid Application Interoperability and providing feedback on the spec. If everything goes as planned for next Monday I should be able to prepare sequence diagram where Application only gets ID Token from IDP and Authorization / Capability from user associated Authorization Agent. Later it would present both to RS associated Authorization Server to receive Access Token from there. I will use combination of UMA2.0 Clam Pushing and OAuth2 Token Exchange. I hope we can align Solid Application Interoperability with (Authorization Capabilities for Linked Data)[https://w3c-ccg.github.io/zcap-ld/] so that Application can use Data Grant issued by user associated Authorization Agent as a claim together with another claim id token, and push / exchange them for Access Token.
BTW implementation should be able to choose to combine IdP and Authorization Agent so that only one consent screen in presented to the user, at the same time we should define things in a way that they can be two separate parties in the flow.