Verification failed for URI
Cody Carmichael
ccarmichael at voalte.com
Thu Aug 2 19:37:50 EDT 2018
> See the MetadataManagementBestPractices [1] topic.
Yes I've read through that, but it didn't provide any use cases. Like if
the SP is going to have lots of people logging in and out, doesn't the SP
metadata need to be gotten with each login? So wouldn't it make sense to
get it dynamically instead of from a static file? Is the metadata something
to identity each user logging in or just the SP itself? These are the dumb
questions I need clarification on.
On Thu, Aug 2, 2018 at 7:27 PM, Tom Scavo <trscavo at gmail.com> wrote:
> On Thu, Aug 2, 2018 at 7:21 PM, Cody Carmichael <ccarmichael at voalte.com>
> wrote:
> > The SP in this case is a product under development by the company I work
> > for. I've been working with the SP's dev for several days on this and
> > unfortunately it's very time sensitive. What would be the more 'usual'
> way
> > to get metadata from the SP? FileBackedHttp? I'm new to most of the
> concepts
> > involved with shibboleth so I don't have a concept of the typical way to
> do
> > things.
>
> See the MetadataManagementBestPractices [1] topic.
>
> From what you've said so far, this sounds like local metadata to me.
>
> Tom
>
> [1] https://wiki.shibboleth.net/confluence/x/JQXKAg
> --
> For Consortium Member technical support, see https://wiki.shibboleth.net/
> confluence/x/coFAAg
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
--
*Cody Carmichael *
Engineering Operations | Voalte
Office: 941-312-2830 | Ext
Email: ccarmichael at voalte.com
<http://www.voalte.com/klas-report-classifies-voalte-as-a-strategic-solution-provider-with-the-most-robust-interfacing/>
<http://www.voalte.com/klas-report-classifies-voalte-as-a-strategic-solution-provider-with-the-most-robust-interfacing/>
<http://www2.voalte.com/l/8232/2017-01-30/6k3skb>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20180802/6b11fe73/attachment.html>
More information about the users
mailing list