One of the issues that seems to have popped up a few times here is that there is no clear way to support multiple audiences with the TokenValidator. This can be a problem when you have a User Pool with more than one client id, which is common for projects that have a REST API for external use.
I had intended to write a new feature branch that would allow for the support of multiple audiences, but as it turns out, there already is support, it's just not documented. So I've added a couple of comments and tests to make it more clear that this is the case.
One of the issues that seems to have popped up a few times here is that there is no clear way to support multiple audiences with the TokenValidator. This can be a problem when you have a User Pool with more than one client id, which is common for projects that have a REST API for external use.
I had intended to write a new feature branch that would allow for the support of multiple audiences, but as it turns out, there already is support, it's just not documented. So I've added a couple of comments and tests to make it more clear that this is the case.