The Trust Router uses Moonshot for authentication, so you would set up credentials for Trust Router communication the same way that you would set up any Moonshot credentials. In the particular case you have mentioned, the Trust Router will be a relying party that is providing the service "trustidentity@<hostname>" (where the hostname is configured in the Trust Router configuration files), and the TID Client would be the client.
I usually focus on getting Moonshot working between the two end-points (testing with gss-client and gss-server), and then I work on getting the trust router running after I have Moonshot working.
Just FYI -- we also have a Management Portal available that provides a graphical, web-application interface for configuring the Trust Router. If you would be interested in learning more about the Management Protocol, we would be happy to provide more information.
Best Regards,
Margaret
On Oct 2, 2014, at 3:35 AM, Frank Tamás <[log in to unmask]> wrote:
> Hello,
>
> I would like to configure our own trust router, but I haven't found documentation about the details. I found example cfg files in the git tree, and after some customization I made trust_router to run, but I have no idea how to create trust router crendential files which are needed to register the trust router client with our own trust router.
>
> Do you have any idea how it can be configured to work properly?
>
> Thanks.
>
> --
> Tamas Frank
> NIIFI
|