IdPv3 Extension Installation and Configuration

[Marvin Addison]

> Assuming subdirectories work in the views, I guess if you use a view name
> of cas/foo that works?

I'm fairly certain that works.

> I think you can avoid that if you use appropriate naming for your flows.
> We have a user-accessible flow repo in conf/flows, and as long as the flow
> files follow the right naming convention, it should work.

I need strict mappings between URI locations and a single flow, e.g.

/idp/cas/login
/idp/cas/serviceValidate
/idp/cas/proxyValidate

I get that I could register a flow simply by putting it in a
well-known location, but I didn't see a way to get the mappings right
without explicitly editing webflow-config.xml.

> You'll also need to plug into relying-party.xml to enable the profiles,
> unless you don't intend any of the existing configuration machinery to be
> used.

Not sure I understand "plug into relying-party.xml." I want to trigger
the attribute resolver, which I guess depends on relying party, but I
haven't done any research on how I would do that. Can you sketch out
some steps or suggest something to review for background?

> I know from our perspective,
> we think protocols should all be *capable* of being secured appropriately,
> including endpoint checks

I agree with that perspective.

M