Re: fun with Capper and OFX financial transaction fetching

--===============2349304175184907790==
Content-Type: multipart/alternative; boundary=001a1145504ccb64fc0528c2ae60

--001a1145504ccb64fc0528c2ae60
Content-Type: text/plain; charset=UTF-8

On Tue, Jan 5, 2016 at 5:46 PM, Marc Stiegler <[email protected]> wrote:

> When Kenton did his first friam presentation on sandstorm, I pressed him
> really hard on how you would ship application-generated webkeys out to the
> users and have accesses directed back to the right app, since I wanted to
> run Capper under sandstorm. It was not possible at that time. I do not know
> if that has changed.
>

Hmm, I don't remember this conversation, so I don't remember exactly what
you're looking for, but Sandstorm offers a number of ways to implement
webkeys. That said, ultimately Sandstorm apps are best-served by letting
the platform implement the access control (which it may do using webkeys or
other methods), so if what you're providing is infrastructure for
capabilities then there may be some friction since Sandstorm is also trying
to provide that.

Anyway, a Sandstorm app can export HTTP-based APIs (for consumption by
machines, not humans) as documented here:
    https://docs.sandstorm.io/en/latest/developing/http-apis/

When you have a Sandstorm app open in your browser, you can click the key
icon in the topbar to get an interface for generating a webkey to the app's
HTTP API. This is displayed in the form "https://hostname/#token", but in
fact the token part goes into the HTTP Authorization header as described in
the docs. (We do this to prevent a human with a web browser from opening
these resources directly, since we want humans to go through the Sandstorm
UI for sandboxing and other purposes.)

If you want to host multiple logical objects within a single grain
(fine-grained app instance), you can implement your own internal
capabilities in the form of unguessable paths. We are working on making it
possible for a grain to export multiple capabilities in a way that
Sandstorm is aware of them (and can provide automatic auditability,
revocability, etc.) but that's not quite ready yet. Usually, it makes more
sense to create a whole new grain for each object.

-Kenton

--001a1145504ccb64fc0528c2ae60
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
ue, Jan 5, 2016 at 5:46 PM, Marc Stiegler <span dir=3D"ltr">&lt;<a href=3D"=
mailto:[email protected]" target=3D"_blank">[email protected]</a>&gt;</=
span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-le=
ft-style:solid;padding-left:1ex"><div dir=3D"ltr"><div><div>When Kenton did=
 his first friam presentation on sandstorm, I pressed him really hard on ho=
w you would ship application-generated webkeys out to the users and have ac=
cesses directed back to the right app, since I wanted to run Capper under s=
andstorm. It was not possible at that time. I do not know if that has chang=
ed.<br></div></div></div></blockquote><div><br></div><div>Hmm, I don&#39;t =
remember this conversation, so I don&#39;t remember exactly what you&#39;re=
 looking for, but Sandstorm offers a number of ways to implement webkeys. T=
hat said, ultimately Sandstorm apps are best-served by letting the platform=
 implement the access control (which it may do using webkeys or other metho=
ds), so if what you&#39;re providing is infrastructure for capabilities the=
n there may be some friction since Sandstorm is also trying to provide that=
.</div><div><br></div><div>Anyway, a Sandstorm app can export HTTP-based AP=
Is (for consumption by machines, not humans) as documented here:<br></div><=
div>=C2=A0 =C2=A0 <a href=3D"https://docs.sandstorm.io/en/latest/developing=
/http-apis/">https://docs.sandstorm.io/en/latest/developing/http-apis/</a><=
br></div><div><br></div><div>When you have a Sandstorm app open in your bro=
wser, you can click the key icon in the topbar to get an interface for gene=
rating a webkey to the app&#39;s HTTP API. This is displayed in the form &q=
uot;<a href=3D"https://hostname/#token">https://hostname/#token</a>&quot;, =
but in fact the token part goes into the HTTP Authorization header as descr=
ibed in the docs. (We do this to prevent a human with a web browser from op=
ening these resources directly, since we want humans to go through the Sand=
storm UI for sandboxing and other purposes.)</div><div><br></div><div>If yo=
u want to host multiple logical objects within a single grain (fine-grained=
 app instance), you can implement your own internal capabilities in the for=
m of unguessable paths. We are working on making it possible for a grain to=
 export multiple capabilities in a way that Sandstorm is aware of them (and=
 can provide automatic auditability, revocability, etc.) but that&#39;s not=
 quite ready yet. Usually, it makes more sense to create a whole new grain =
for each object.</div><div><br></div><div>-Kenton</div></div></div></div>

--001a1145504ccb64fc0528c2ae60--

--===============2349304175184907790==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
cap-talk mailing list
[email protected]
http://www.eros-os.org/mailman/listinfo/cap-talk

--===============2349304175184907790==--