Hi Ryan
Did you get this working, I have exactly the same issue, flexible JID works
fine internally, when the service discovery is done, it presents the actual
user id and password prompt, however when using MRA, it does its service
discovery but prompts the email address and password field which
I can confirm that FJID is not supported over MRA. There is a bug ID for an
enhancement request. It's only got 10 case on it though so you might want to
jump on that wagon ;) squeaky wheel gets the attention and all.
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuy33691/?reffering_site=d
Hi Ryan
Thanks for your reply, thats saved me a lot of time. I can't believe this
is not supported. I'll log a case and get it added to the enhancement.
Regards
Nick
On 27 February 2017 at 12:14, Ryan Huff wrote:
> I can confirm that FJID is not supported over MRA. There is a bug ID for
> an
It seems obvious to me (and apparently you) that it should work.
As I understand it FJID was more of an after thought and was intended to allow
XMPP routing to an alternate alias in federated scenarios.
However, that's a bit like letting the cat out of the bag ... if your going to
make it 'sort
This comes back to Cisco failing what I call the apple test. Give someone a
piece of tech and watch what they try to do with it in the first couple of
hours. If you can check the box to yes on all those things, then you got a
winning product.
This goes to the whole UDS vs. LDAP. Customers want
At least the last part is fixed now with the UDS Proxy features.
On Mon, Feb 27, 2017 at 11:38 AM, Heim, Dennis wrote:
> This comes back to Cisco failing what I call the apple test. Give someone
> a piece of tech and watch what they try to do with it in the first couple
> of hours. If you can ch
