Partner-onboarder issue

parandhaman · September 15, 2025, 5:34am

ok Sir - Me and my team will join ..

Mahesh-Binayak · September 15, 2025, 8:15am

Sure @parandhaman
Here is the meeting link

from 3.00 pm to 3.30 IST (Today)

Mahesh-Binayak · September 15, 2025, 9:55am

The tables to check are
1.Auth_policy
2.policy_group
3.Partner-policy
4.partner
From these tables delete the data related to keybinding partner and retry onboarding.
@parandhaman

parandhaman · September 15, 2025, 11:23am

Thank you sir- will check and revert back

parandhaman · September 18, 2025, 5:32am

Dear Sir - i deleted records form the above tables after each try , now i dont see reports getting generated in the bucket..

Mahesh-Binayak · September 22, 2025, 7:41am

Hi @parandhaman . Can u share logs from the job’s execution. It could be an issue with your set up .

Thanks and regards
Mahesh

parandhaman · September 22, 2025, 8:05am

kubectl logs job/partner-onboarder-mimoto-keybinding -n onboarder
Onboarding default partners
KEYCLOAK_CLIENT = mosip-deployment-client
KEYCLOAK ADMIN USER : admin
URL : https://api-internal.sandbox.oasys.net and https://api.sandbox.oasys.net
-----BEGIN CERTIFICATE-----
MIIDrTCCApWgAwIBAgIUAJHNEG/JRIYCtcCwFA/4dQC4nAkwDQYJKoZIhvcNAQEL
BQAwZjELMAkGA1UEBhMCSU4xCzAJBgNVBAgMAlROMQwwCgYDVQQHDANDSE4xDjAM
BgNVBAoMBU1PU0lQMQ4wDAYDVQQLDAVNT1NJUDEcMBoGA1UEAwwTKi5zYW5kYm94
Lm9hc3lzLm5ldDAeFw0yNTA4MDgxMjQ2NDVaFw0yNzA3MDkxMjQ2NDVaMGYxCzAJ
BgNVBAYTAklOMQswCQYDVQQIDAJUTjEMMAoGA1UEBwwDQ0hOMQ4wDAYDVQQKDAVN
T1NJUDEOMAwGA1UECwwFTU9TSVAxHDAaBgNVBAMMEyouc2FuZGJveC5vYXN5cy5u
ZXQwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDot0yWkz+A/1rNKFmO
sSFK7tubpSj7ECb9II87ryDe8imi7zox6JyBu+BWCG0AFx30NG00RHXIDYrqfy9Y
Rjzc5vLcOUfDREHghpDZzn3OA5LFcmsKilhSq2p1dXEuhO2D/FlpfBnGPSgHP/4D
qDblR6X4cVn9M35X1F+z9O/dxoU8YOFtdKU4U2DfKJj0UkH+UxvHm9WN/IlkZppA
vveSjbHESJXF6zoWHoM0MBD6kvwekcZnh4yRFuR930GYo4eMMh/EKEVjTOaPgq/i
4FKm0HHezUYVB5BTV/CB0EDNapMKhk1fniLLxyXvkiAmnd/OZO4EAVC0lggrpvZ8
Ty0pAgMBAAGjUzBRMB0GA1UdDgQWBBSOx7Loe+7FQxzszOK2n6tBXGCasDAfBgNV
HSMEGDAWgBSOx7Loe+7FQxzszOK2n6tBXGCasDAPBgNVHRMBAf8EBTADAQH/MA0G
CSqGSIb3DQEBCwUAA4IBAQBqBkf/x/hUpYZzuveD3vglis2+/ejLw8NpuSoJ4nGF
Y89XFDu4tdfOsVSBjFJGSE4yuFiAga3MXZOB3vtXfQANoGmTWMe/NdzgenzBOi3o
gHVTOif8jwR3sNZ+pvIXuFBQqxJkPDZWyGTNVuPjdp5zbl/vkJExp8WH3GFb6l7+
sros32x8/QRkPyA/+xVQ2E1vpHLrtkYaKxYm9qHBBq7etlCJVR/OzB4t+tFiWK/l
poR8b4i4kCo5lZqhutyUJUKr6FoCnS7m3hG7jNs8f8dmgfqPixbDRzvLErP3Ev77
btq+1OL1BaEd1LMI8L316FNLaW4o72/xxF2n8mqflQiZ
-----END CERTIFICATE-----
Onboarding Mimoto Keybinding partner
mpartner-default-mimotokeybinding is the name of the partner.
updating conf
==================== Creating CA certificate
==================== Creating partner certificate
Certificate request self-signature ok
subject=C = IN, ST = Kar, L = Blr, O = IITB, CN = mpartner-default-mimotokeybinding-Client
Cert generation complete

onboarding Copy

❏ create_keycloak_user
↳ login-to-keycloak-as-admin
POST https://iam.sandbox.oasys.net/auth/realms/master/protocol/openid-connect/token [200 OK, 2.56kB, 252ms]
┌
│ ‘eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJWd
│ 3VUMlNtdEJNdmQ3RHlOVHVPSUNBdW03djRuSmxYTjZJdUtRNU43Qzc
│ 0In0.eyJleHAiOjE3NTgxNzMzNzUsImlhdCI6MTc1ODE3MzMxNSwia
│ nRpIjoiMzA0YjQxNGMtZjI5MS00OWMzLWEzNTMtMTQ3NzUzMmE1ZGM
│ 2IiwiaXNzIjoiaHR0cHM6Ly9pYW0uc2FuZGJveC5vYXN5cy5uZXQvY
│ XV0aC9yZWFsbXMvbWFzdGVyIiwic3ViIjoiZGQ5MmExNmItNTY3MC0
│ 0ODU5LThjODAtNzM0MDdlOGUyY2ZhIiwidHlwIjoiQmVhcmVyIiwiY
│ XpwIjoiYWRtaW4tY2xpIiwic2Vzc2lvbl9zdGF0ZSI6ImFkYTVkMGI
│ 4LTAyNzYtNGJmMC04ZWI1LTU0Mzk5ODk0MGE3MCIsImFjciI6IjEiL
│ CJzY29wZSI6InByb2ZpbGUgZW1haWwiLCJzaWQiOiJhZGE1ZDBiOC0
│ wMjc2LTRiZjAtOGViNS01NDM5OTg5NDBhNzAiLCJlbWFpbF92ZXJpZ
│ mllZCI6ZmFsc2UsInByZWZlcnJlZF91c2VybmFtZSI6ImFkbWluIn0
│ .MTVsYZo_KOrTjXqjH77D0aMHF8wwh3I4Jd0Hm99mQNJ47RVjipzTg
│ yL_PnbmxIbc7hcxhIw1bDzyb94GdxVYesEWv2Uj8SrCIng8Jbz1LFW
│ 1XumNuQhptlZjqM2lnOKKCXJVw9bThsrTh5JzkRNMU8r6aWbTMwoou
│ 3NbRjRI8MHbPEEziVlpcBRerV0zQLgarvlWyp1tmpyIflLO4QuL356
│ HHNnEmrjOQ9yo-iD8cM7Ml7Ojx7Y_OGZr4BprV1Qdjw1srTKzv4V1s
│ xuQ37-Xhix-twudAYB9w8Co67_l1eYGbDqqnD14ifHEdFlNWrsBUE_
│ DldewwRAPsh9TQadVSQ’
└

↳ create-user
POST https://iam.sandbox.oasys.net/auth/admin/realms/mosip/users [409 Conflict, 425B, 15ms]

↳ get-user-details
GET https://iam.sandbox.oasys.net/auth/admin/realms/mosip/users?username=mpartner-default-mimotokeybinding [200 OK, 814B, 26ms]
┌
│ ‘ca7d525f-0fa2-49b6-982c-4ff6dadfdfc5’
└

↳ get-role-id-for-all-roles
GET https://iam.sandbox.oasys.net/auth/admin/realms/mosip/roles [200 OK, 17.85kB, 21ms]
┌
│ ‘b2eca2c5-5bf6-4292-b32f-0f4902ab0df6’, ‘AUTH_PARTNER’
│ ‘cb0ea45d-3fcf-4d15-9dd2-e1c5ac885dc5’, 'PARTNER_ADMIN
│ ’
└

↳ assign-role-to-user
POST https://iam.sandbox.oasys.net/auth/admin/realms/mosip/users/ca7d525f-0fa2-49b6-982c-4ff6dadfdfc5/role-mappings/realm [204 No Content, 327B, 31ms]

❏ create/publish_policy_group_and_policy
↳ authenticate-as-policy-manager
POST https://api-internal.sandbox.oasys.net/v1/authmanager/authenticate/internal/useridPwd [200 OK, 3.3kB, 112ms]

↳ create-policy-group
POST https://api-internal.sandbox.oasys.net/v1/policymanager/policies/group/new [200 OK, 691B, 71ms]
✓ set policy id

↳ create-policy
┌
│ ‘{“id”:“”,“metadata”:null,“request”:{“name”:“{{policy-
│ name}}”,“desc”:“{{policy-name}} Policy”,“policies”:{“a
│ uthTokenType”:“policy”,“allowedKycAttributes”:[{“attri
│ buteName”:“fullName”},{“attributeName”:“gender”},{“att
│ ributeName”:“phone”},{“attributeName”:“email”},{“attri
│ buteName”:“dateOfBirth”},{“attributeName”:“city”},{“at
│ tributeName”:“face”},{“attributeName”:“addressLine1”},
│ {“attributeName”:“individual_id”}],“allowedAuthTypes”:
│ [{“authSubType”:“IRIS”,“authType”:“bio”,“mandatory”:fa
│ lse},{“authSubType”:“FINGER”,“authType”:“bio”,“mandato
│ ry”:false},{“authSubType”:“”,“authType”:“otp”,“mandato
│ ry”:false},{“authSubType”:“FACE”,“authType”:“bio”,“man
│ datory”:false},{“authSubType”:“”,“authType”:“otp-reque
│ st”,“mandatory”:false},{“authSubType”:“”,“authType”:“k
│ yc”,“mandatory”:false},{“authSubType”:“”,“authType”:“d
│ emo”,“mandatory”:false},{“authSubType”:“”,“authType”:"
│ kycauth",“mandatory”:false},{“authSubType”:“”,“authTyp
│ e”:“kycexchange”,“mandatory”:false},{“authSubType”:“”,
│ “authType”:“keybinding”,“mandatory”:false},{“authSubTy
│ pe”:“”,“authType”:“kbt”,“mandatory”:false},{“authSubTy
│ pe”:“”,“authType”:“wla”,“mandatory”:false},{“authSubTy
│ pe”:“”,“authType”:“vciexchange”,“mandatory”:false}]},"
│ policyGroupName":“{{policy-group-name}}”,“policyType”:
│ “Auth”,“version”:“1.1”},“version”:“1.0”,“requesttime”:
│ “{{$isoTimestamp}}”}’
└
POST https://api-internal.sandbox.oasys.net/v1/policymanager/policies [200 OK, 778B, 1960ms]
✓ set policy id
✓ set policy name

↳ publish-policy-and-policy-group
POST https://api-internal.sandbox.oasys.net/v1/policymanager/policies/97331/group/59305/publish [200 OK, 2.38kB, 249ms]

❏ partner_self_registration
↳ partner-self-registration
POST https://api-internal.sandbox.oasys.net/v1/partnermanager/partners [200 OK, 570B, 380ms]

❏ cert_upload
↳ authenticate-to-upload-certs
POST https://api-internal.sandbox.oasys.net/v1/authmanager/authenticate/internal/useridPwd [200 OK, 3.31kB, 108ms]

↳ upload-ca-certificate
POST https://api-internal.sandbox.oasys.net/v1/partnermanager/partners/certificate/ca/upload [200 OK, 563B, 157ms]
✓ Upload Successfull or Certificate is already present in DB

↳ upload-leaf-certificate
POST https://api-internal.sandbox.oasys.net/v1/partnermanager/partners/certificate/upload [200 OK, 613B, 1641ms]
1⠄ TypeError in test-script

┌─────────────────────────┬─────────────────────┬────────────────────┐
│ │ executed │ failed │
├─────────────────────────┼─────────────────────┼────────────────────┤
│ iterations │ 1 │ 0 │
├─────────────────────────┼─────────────────────┼────────────────────┤
│ requests │ 13 │ 0 │
├─────────────────────────┼─────────────────────┼────────────────────┤
│ test-scripts │ 24 │ 1 │
├─────────────────────────┼─────────────────────┼────────────────────┤
│ prerequest-scripts │ 25 │ 0 │
├─────────────────────────┼─────────────────────┼────────────────────┤
│ assertions │ 4 │ 0 │
├─────────────────────────┴─────────────────────┴────────────────────┤
│ total run duration: 32.9s │
├────────────────────────────────────────────────────────────────────┤
│ total data received: 28.34kB (approx) │
├────────────────────────────────────────────────────────────────────┤
│ average response time: 386ms [min: 15ms, max: 1960ms, s.d.: 615ms] │
└────────────────────────────────────────────────────────────────────┘

failure detail

TypeError
Cannot read properties of null (reading ‘signedCertificateData’)
at test-script
inside “cert_upload / upload-leaf-certificate”
Updating Mimoto Wallet Binding Partner API Key
Error from server (Forbidden): error when creating “STDIN”: secrets is forbidden: User “system:serviceaccount:onboarder:partner-onboarder” cannot create resource “secrets” in API group “” in the namespace “mimoto”
Mimoto Wallet Binding Partner API Key updated successfully

=========================== PUSHING REPORTS TO S3 ================================================

S3_HOST: http://minio:9000

S3_REGION:

S3_USER_KEY: admin

S3_USER_SECRET: AVuTSm33vr

S3_BUCKET_NAME: onboarder

mc: Unable to initialize new alias from the provided credentials. Get “http://minio:9000/probe-bsign-26z4vnby9ytsj6d9z5dv9a9s9qzyuq/?location=”: dial tcp: lookup minio on 10.43.0.10:53: no such host.
mc: Unable to make bucket s3/onboarder. The AWS Access Key Id you provided does not exist in our records.
/home/mosip/reports/mimoto-keybinding.html → s3/onboarder/reports/mimoto-keybinding.html
mc: Failed to copy /home/mosip/reports/mimoto-keybinding.html. The AWS Access Key Id you provided does not exist in our records.

Reports pushed to minio
Onboarding completed!

Mahesh-Binayak · September 22, 2025, 11:51am

@parandhaman you can clearly see the error here. Its some issue with your connection with the minio bucket.see if you can fix that first.

parandhaman · September 23, 2025, 6:04am

Dear Sir-The issue is that the NodePorts exposed by the MinIO service in k8 and the upstream servers configured in NGINX are not aligned, I am working on correcting the upstreams to route traffic to appropriate ports.

parandhaman · November 25, 2025, 4:26am

@Mahesh-Binayak Sir.. Above issue still persist,Please let me know your available timings.

Mahesh-Binayak · November 25, 2025, 1:38pm

Hi @parandhaman
It seems there is another error in the api itself.
Where it shows the signed certificate error .
Can we check why that happened ?

Topic		Replies	Views
MOSIP 1.2.0.1-B3 partner onboard issue Developer	6	429	August 23, 2023
Partner Management Portal - Doesn't show dashboard, Can't create Device nor SBI	19	786	September 29, 2023
IDA-MPA-001 Signature Verification Failure Support	33	318	November 30, 2025
Error while uploading client.cer	4	271	September 29, 2023
[12.0.1] partner-onboarder installation errors / misisng minimoto Support	3	175	April 25, 2024

Partner-onboarder issue

failure detail

Related topics