It is actually generated for you. I turned it off for the demo. So you can choose between JSON Web Tokens (JWT),
Session-based authentication,
OAuth2 and OpenID Connect,
JHipster User Account and Authentication (UAA)
as described here: jhipster.tech/security/
Hi Gary. Yes correct, the Custom Connector would have to make provision for the authentication. Depending on the connector type, the users who consume the connections might have to specify logon credentials as well.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
How would you add some form of security to that API?
It is actually generated for you. I turned it off for the demo. So you can choose between JSON Web Tokens (JWT),
Session-based authentication,
OAuth2 and OpenID Connect,
JHipster User Account and Authentication (UAA)
as described here: jhipster.tech/security/
Excellent. Follow up. How would this be handled client side? In the custom connector or the PowerApp?
Hi Gary. Yes correct, the Custom Connector would have to make provision for the authentication. Depending on the connector type, the users who consume the connections might have to specify logon credentials as well.