[
https://issues.apache.org/jira/browse/STONEHENGE-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicholas A Hauenstein updated STONEHENGE-124:
---------------------------------------------
Attachment: WSAS_endpoing_mapping.patch
Here is a better solution for the endpoint mapping in the .NET client app. It
includes a separate configuration for the WSAS Business Service that doesn't
require signature confirmation. This will allow for purely UI-based swapping
between endpoints, instead of cracking open the configuration file for one of
them.
It would also be ideal to configure this endpoint to request claims from the
WSAS Active STS implementation (assuming there is one) as well. Currently it's
pointing at the .NET Active STS. Any thoughts about this? It's not being used
otherwise.
I am not sure what the endpoint is for the WSAS Active STS though, or if it
needs to be configured in any way before it is ready for use.
Additionally it might make sense to make an endpoint mapping for Metro that
points to the Metro Active STS implementation.
> Endpoint mapping missing for WSAS_BS in .NET Client Config
> ----------------------------------------------------------
>
> Key: STONEHENGE-124
> URL: https://issues.apache.org/jira/browse/STONEHENGE-124
> Project: Stonehenge
> Issue Type: Bug
> Components: DOTNET_CLIENT
> Affects Versions: M2
> Reporter: Nicholas A Hauenstein
> Assignee: Nicholas A Hauenstein
> Fix For: M2
>
> Attachments: WSAS_endpoing_mapping.patch
>
> Original Estimate: 0.03h
> Remaining Estimate: 0.03h
>
> The endpoint mapping for the WSAS BS endpoint is missing from the .NET Client
> config.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
