-
-
Notifications
You must be signed in to change notification settings - Fork 395
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebApi of remote start, remote stop and connector status #1291
base: master
Are you sure you want to change the base?
Conversation
…and UnlockConnector
…geBoxId, Integer connectorId) and getOcppTagOfTransaction(Integer transaction_pk);
…tor for RemoteStart, RemoteStop and UnlockConnector
…tation o ChargeBoxPk;
…JasonIgnor annotation to ChargeBoxPk;
…ere is already a active transaction, methode postUnlockCon checks no that there is no active transaction, removed the ocpp tag check; Added comments
…TaskRestController class
…eferZero and PreferOthersWithStatusOfZero
…eIfMultiple at master
@goekay Please review, this PR is improving the product. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
set the api-key in the config file |
steve changed to basic auth for the api. I haven't test it with the basic auth! There may be more problems. |
Yeah that worked. Thank you so much. |
Hello, thank you ` @OverRide
|
In the discussion of "switch to basic auth for API access #1545" is the role and background for the change already addressed. In the appended code it only seems that the api-password is checked against the password. webUserService.loadUserByUsernameForApi reads the api-password from the database and stores it as 'password' in userDetails (just (re)using the existing class) If you working with a existing database, please check if Steve had ported the api-key into the web-user api-password. |
Adding a Webapi for RemoteStart, RemoteStop and Connector Status. The RestApi behaves similarly to the website. RemoteStart and RemoteStop respond with the task ID that can be used to check the result of TransactionStart/TransactionStop.