Matt McFarland

@flavorjones Thank you for the sanity check! Please let me know if there's any additional legwork I can do to help out.

@flavorjones Thank you! That's great to hear.

@flavorjones Ah shucks. Thank you for pulling on this thread and diving deep into the rabbit hole. I think we will investigate an array of possible solutions including a SAX...

+1

For what it’s worth. The aws2 cli is now out in beta, which support aws sso commands and auth. There’s also support for the aws sso service in some aws...

I'm using Slick 3.0 and seeing the same error. Why is this happening? Is there a best-practice work-around until a fix is introduced?