Not logged in : Login

About: Embedded HTML5 Microdata Statement 4     Goto   Sponge   NotDistinct   Permalink

An Entity of Type : rdf:Statement, within Data Space : associated with source document(s)

  • Embedded HTML5 Microdata Statement 4
described by
  • This raises another question - in order to allow the web-app’s server to link the WebId with some internal account, the web-app/browser must be able to prove it’s WebId to the server. Unfortunately the server was never involved in the login process which is strictly confined to the browser and the web-app’s javascript code, so the server has no knowledge of that process. The web-app cannot simply POST it’s WebId to the server since anybody else would be able to do the same with any WebId they wanted. Neither can the web-app build a signed OpenID Connect token to POST as the signing key would be available to anyone that can read the javascript code. So how does the web-app / browser-javascript-code prove the WebId it received to the server it is served from? Is there any token of some sort the web-app can send to the server and allow it to validate it with the remove WebId identity provider?
is topic of
is container of of
Faceted Search & Find service v1.17_git55 as of Mar 01 2021

Alternative Linked Data Documents: ODE     Content Formats:       RDF       ODATA       Microdata      About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data] Valid XHTML + RDFa
OpenLink Virtuoso version 08.03.3320 as of Jan 15 2021, on Linux (x86_64-generic-linux-glibc25), Single-Server Edition (7 GB total memory)
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2021 OpenLink Software