mirror of
https://github.com/mainflux/mainflux.git
synced 2025-04-26 13:48:53 +08:00

* Add both an ID and an Email to API key requests Signed-off-by: dusanb94 <dusan.borovcanin@mainflux.com> * Use return UserIdentity response Signed-off-by: dusanb94 <dusan.borovcanin@mainflux.com> * Replace GetValue with GetEmail Signed-off-by: dusanb94 <dusan.borovcanin@mainflux.com> * Refactor Mainflux Key Add `Subject` field and reorganize Key manipulation. **Remove backward compatibility** Signed-off-by: dusanb94 <dusan.borovcanin@mainflux.com> * Fix service test Signed-off-by: dusanb94 <dusan.borovcanin@mainflux.com> * Fix DB tests Signed-off-by: dusanb94 <dusan.borovcanin@mainflux.com> * Fix API tests Signed-off-by: dusanb94 <dusan.borovcanin@mainflux.com> * Fix JWT tests Signed-off-by: dusanb94 <dusan.borovcanin@mainflux.com> * Uncomment and fix API tests Signed-off-by: dusanb94 <dusan.borovcanin@mainflux.com> * Fix SQL statements alignment Signed-off-by: dusanb94 <dusan.borovcanin@mainflux.com> * Fix Issue method docs Signed-off-by: dusanb94 <dusan.borovcanin@mainflux.com> * Fix Retrieve API and API docs Signed-off-by: dusanb94 <dusan.borovcanin@mainflux.com> * Update tests Signed-off-by: dusanb94 <dusan.borovcanin@mainflux.com>
52 lines
1.0 KiB
Protocol Buffer
52 lines
1.0 KiB
Protocol Buffer
// Copyright (c) Mainflux
|
|
// SPDX-License-Identifier: Apache-2.0
|
|
|
|
syntax = "proto3";
|
|
|
|
package mainflux;
|
|
|
|
import "google/protobuf/empty.proto";
|
|
|
|
service ThingsService {
|
|
rpc CanAccessByKey(AccessByKeyReq) returns (ThingID) {}
|
|
rpc CanAccessByID(AccessByIDReq) returns (google.protobuf.Empty) {}
|
|
rpc Identify(Token) returns (ThingID) {}
|
|
}
|
|
|
|
service AuthNService {
|
|
rpc Issue(IssueReq) returns (Token) {}
|
|
rpc Identify(Token) returns (UserIdentity) {}
|
|
}
|
|
|
|
message AccessByKeyReq {
|
|
string token = 1;
|
|
string chanID = 2;
|
|
}
|
|
|
|
message ThingID {
|
|
string value = 1;
|
|
}
|
|
|
|
message AccessByIDReq {
|
|
string thingID = 1;
|
|
string chanID = 2;
|
|
}
|
|
|
|
// If a token is not carrying any information itself, the type
|
|
// field can be used to determine how to validate the token.
|
|
// Also, different tokens can be encoded in different ways.
|
|
message Token {
|
|
string value = 1;
|
|
}
|
|
|
|
message UserIdentity {
|
|
string id = 1;
|
|
string email = 2;
|
|
}
|
|
|
|
message IssueReq {
|
|
string id = 1;
|
|
string email = 2;
|
|
uint32 type = 3;
|
|
}
|