Hi,

Planning to use this library to integrate with react-native-exposure-notification-service of our own app. I have couple of questions.

1. can I use these APIs to integrate with the exposure notification service?
2. is there any way I can import indexes and collection data structure to firestoreDB?
3. is there any way I can create testing user to test these services?
4. Is there any API I can use as keyServerUrl for the service?

Your input will really helpful.

--
Thanks in Advance,
Shashi

Bug Details

• The status code of the /auth/admin/login（POST） response is returned as 201 and the data is also returned.
  • By Swagger's definition, the status code is 204, with no response data.

Expected value

• As defined in Swagger, the status code returns 204 as a response

Reproduction method

1. Open an API test tool such as Postman and configure the following
2. Enter the URL. https://api-dev.mamori-i.jp/auth/admin/login
3. Obtain an access token from the authentication screen
4. Set the access token obtained in 3 as the Bearer Token
5. Send the API

実装の終わっていないAPI

実装の終わっていないAPIと完了時期を教えて下さい。
以下2つが終わっていない認識ですが、あってますか？

• 陽性登録（保健所トークン申告）
  • swaggerに記載あり（/users/me/health_center_tokens）
• 陽性判定の削除 (同意撤回)
  • swaggerに記載なし

陽性登録（保健所トークン申告）についての質問

healthCenterTokenは制限（DBにすでに存在するものなど）や、命名規則がありますか？

Should support:

• size
• offset
• sort

• Uploading exposure(濃厚接触) temp IDs list for the past 14 days from the mobile to the backend when the user become positive.
• user consent is required. optin, can be optout as well
• only positives invoke this API.
• the uploaded data will be used by mainly the cluster analysis team.

Bug Details

• The status code of the /admins/positives（POST） response is returned as 201.
  • By Swagger's definition, the status code is 204, with no response data.

Implementation environment

• Postman（Mac）

Expected value

• As defined in Swagger, the status code returns 204 as a response

Reproduction method

1. Open an API test tool such as Postman and configure the following
2. Enter the URL. https://api-dev.mamori-i.jp/admins/positives
3. Include the following in the Request body

{
  "phoneNumber": "+819078772537"
}

4. Obtain an access token from the authentication screen
5. Set the access token obtained in 3 as the Bearer Token
6. Send the API

APIs with different definitions of test results and swagger

The following is a summary of the results of the API unit test and the API with different definitions in swagger.
I think it's probably an omission in swagger, so please fix the definition.

• /admins/users/（GET）
  • Success
    • accessControlList(l.5)（#/components/schemas/Admin）
• /admins/users/{userId}（GET）
  • Success
    • accessControlList(l.28)（#/components/schemas/Admin）
  • Client Error
    • 404
      • usecase : invalid userId (l.30)
• /admins/users/{userId}（DELETE）
  • Client Error
    • 404
      • usecase : invalid userId (l.34)
• /admins/prefectures/（GET）
  • Success
    • accessControlList(l.59)（#/components/schemas/Prefecture）
• /admins/prefectures/{prefectureId}（GET）
  • Success
    • accessControlList(l.63)（#/components/schemas/Prefecture）
  • Client Error
    • 404
      • usecase : invalid prefectureId (l.64)
• /admins/prefectures/{prefectureId}（PATCH）
  • Client Error
    • 404
      • usecase : invalid prefectureId (l.68)

Bug Details

In this API, the organization information of the administrator's target organization（28B41D0F） is obtained, not the organization information of the organizationId（448DC39B） passed as a parameter.

Implementation environment

• Postman（Mac）

Expected value

The organization information of the organizationId passed as a parameter is retrieved.

Reproduction method

Open an API test tool such as Postman and configure the following

1. Enter the URL. https://api-dev.mamori-i.jp/admins/organizations?organizationId=448DC39B
2. Obtain an access token from the authentication screen
3. Set the access token obtained in 2 as the Bearer Token
4. Send the API

Bug Details

• Passing a registered email address to the request body and executing the API（/admins/users（POST）） returns an status code（404）.
  • A status code (201) will be returned as well as an unregistered email address.

Expected value

• The status code returns 201 as a response

Reproduction method

1. Open an API test tool such as Postman and configure the following
2. Enter the URL. https://api-dev.mamori-i.jp/admins/positives
3. Include the following in the Request body （unregistered email）

{
  "email": "[email protected]"
}

4. Obtain an access token from the authentication screen
5. Set the access token obtained in 3 as the Bearer Token
6. Send the API
7. Send the API again.

Add endpoint to support creation of new admin users.
POST admins/users

• an admin user input phone no through admin panel to make phone no person as postive
  • lookup uid with phone no in firebase auth
    • https://firebase.google.com/docs/reference/admin/node/admin.auth.Auth#getuserbyphonenumber
  • update userStatus to postive by the uid.

I saw this strange error in the logs.
We might face this sooner or later.
We can investigate this later if we run in to it quite often. 🙏

2020-04-24T11:23:48.889Z	690de5f8-b3e5-4b4f-b238-0af7bf0c6d13	ERROR	Uncaught Exception 	
{
    "errorType": "Error",
    "errorMessage": "14 UNAVAILABLE: No connection established",
    "code": 14,
    "details": "No connection established",
    "metadata": {
        "internalRepr": {},
        "options": {}
    },
    "stack": [
        "Error: 14 UNAVAILABLE: No connection established",
        "    at Object.callErrorFromStatus (/opt/nodejs/node_modules/@grpc/grpc-js/build/src/call.js:30:26)",
        "    at Object.onReceiveStatus (/opt/nodejs/node_modules/@grpc/grpc-js/build/src/client.js:327:49)",
        "    at Object.onReceiveStatus (/opt/nodejs/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:303:181)",
        "    at Http2CallStream.outputStatus (/opt/nodejs/node_modules/@grpc/grpc-js/build/src/call-stream.js:114:27)",
        "    at Http2CallStream.maybeOutputStatus (/opt/nodejs/node_modules/@grpc/grpc-js/build/src/call-stream.js:153:22)",
        "    at Http2CallStream.endCall (/opt/nodejs/node_modules/@grpc/grpc-js/build/src/call-stream.js:140:18)",
        "    at Http2CallStream.cancelWithStatus (/opt/nodejs/node_modules/@grpc/grpc-js/build/src/call-stream.js:441:14)",
        "    at ChannelImplementation.tryPick (/opt/nodejs/node_modules/@grpc/grpc-js/build/src/channel.js:214:32)",
        "    at ChannelImplementation._startCallStream (/opt/nodejs/node_modules/@grpc/grpc-js/build/src/channel.js:244:14)",
        "    at Http2CallStream.start (/opt/nodejs/node_modules/@grpc/grpc-js/build/src/call-stream.js:418:22)"
    ]
}

Found these related issues on github.
grpc/grpc-node#1064
googleapis/nodejs-pubsub#890

Bug Details

The API in /admins/organizations (POST) was able to create an organization with the same name and the name was not checked for duplication.

Implementation environment

• Postman（Mac）

Expected value

If an already registered name is POSTed, an error message such as "The organization name you entered is already registered" will be returned.

Reproduction method

Open an API test tool such as Postman and configure the following

1. Enter the URL. https://api-dev.mamori-i.jp//admins/organizations
2. Include the following in the Request body （unregistered email）
   { "name": "test organization", "message": "This is optional message. Can be later added via PATCH." }
3. Obtain an access token from the authentication screen
4. Set the access token obtained in 3 as the Bearer Token
5. Send the API
6. Send the API again.

Bug Details

• The status code of the /auth/login（POST） response is returned as 201 and the data is also returned.
  • By Swagger's definition, the status code is 204, with no response data.

Expected value

• As defined in Swagger, the status code returns 204 as a response

Reproduction method

1. Open an API test tool such as Postman and configure the following
2. Enter the URL. https://api-dev.mamori-i.jp/auth/login
3. Include the following in the Request body

{
  "prefecture": 1,
  "job": "公務員"
}

4. Obtain an access token from the authentication screen
5. Set the access token obtained in 3 as the Bearer Token
6. Send the API

1. Serverless Framework Pro https://serverless.com/pricing/
2. Datadog for Serverless https://www.datadoghq.com/ja/blog/datadog-for-serverless/
3. New Relic Serverless for AWS Lambda https://newrelic.co.jp/products/serverless-aws-lambda
4. AWS X-Ray https://aws.amazon.com/jp/xray/

フロントエンドチームで実施

Bug Details

• Sending a request with the /users/me/profile (PATCH) API without a request body will return a status code of 200
  • The status code (400) will be returned.

Implementation environment

• Postman（Mac）

Expected value

• The status code returns 400 as a response.

Reproduction method

1. Open an API test tool such as Postman and configure the following
2. Enter the URL. https://api-dev.mamori-i.jp//users/me/profile
3. Obtain an access token from the authentication screen
4. Set the access token obtained in 3 as the Bearer Token
5. Send the API