Hello Shindig community, What would be the use case for allowing gadget-specific RSA consumer secrets? Other than for testing sake, I can't think of a scenario where a production Shindig deployment would use private/public key pairs on a per gadget basis. It would seem that the consumer would (should?) provide the same public key to all service providers.
In my Shindig implementation, I'm thinking of hiding the option to enter a consumer secret if the keyType is RSA and always use the secret (RSA private key) defined by shindig.signing.key-file in shindig.properties. Any reason why this would be a bad idea? Perhaps I'm missing something obvious here, so thought I'd seek guidance from the community. TIA, Dennis
