Installation Resources

[Fred Newtz (frnewtz)]

On 2/10/17, 11:27 AM, "users on behalf of Cantor, Scott" <users-bounces at shibboleth.net on behalf of cantor.2 at osu.edu> wrote:

    On 2/10/17, 12:55 PM, "users on behalf of Fred Newtz (frnewtz)" <users-bounces at shibboleth.net on behalf of frnewtz at cisco.com> wrote:
    

>    If you understand SAML and the systems you're connecting to thoroughly, and you have the necessary experience with Java server operation and Spring >configuration, then I would be happy to respond to specific critiques that you think represent an assumption that one has a PhD in Shibboleth.

I just want to say that the documentation that is currently available is very good.  There is no doubt about it.  I realize a massive amount of man power has been put into the documentation by people who are already very familiar with the Shibboleth in general.  

I have to admit I do not have the background in SAML.  I have a basic understand of it, but that is it.  I am working on documenting the integration of Shibboleth IdP with a third party SP.  Which requires a working installation of Shibboleth before I get much further.  The technologies used by Shibboleth are all the ones I have used the least in my 24+ year professional career.  However, I know I am not having issues with the installation portion of Shibboleth and communication is happening and working just fine.  
    
> After initial install and status page testing, you go through each major piece and configure them, and then test and use the logs. I don't really know what else >you're looking for because you aren't asking any specific questions.

Just an order of operations for configuration honestly.  If the links in the documentation are already in that order then great.  I will keep plugging along until I get a win here.
    

>    The software does not provide a mechanism for "partial" use, at least not generally. All of the critical components (basic setup, authentication, attribute >fetch, attribute release) have to be working to end up with a meaningful outcome. If you want to decompose it, then you can probably either focus on >authentication first, or attributes first. Authentication is mostly testable if you have an SP or mock up a link. Attributes are testable with the aacli command line >tool to exercise basic operation. That's really it.
 
I love the aacli tool.  I was able to make a query, but it just returns the URL.  I don’t get any errors and I do not get any SAML output though either.  So knowing what to do in that case would be a pretty cool thing to know.

> You can't document a system by writing a single document that only hits 10% of it. That comes later, as a How-To or example, and it is a bonus.
   
  Yes!  I definitely agree.  That is definitely more of a how-to document.  That would be an awesome link to have though!


Thanks Scott!  I will get specific questions together and we can go from there.

Thanks,

Fred