Hi Omindu,
We have tried to use the new MePIN endpoint for API version 4 . But we
got error
from Mepin back end as {"status":"error","status_text":"Service plan does
not permit requested action. Please contact [email protected]"}.
Seems we need a commercial account for the Mepin API access. So, If we get
an account then we can update the Mepin authenticator.
Thanks,
On Tue, Jul 24, 2018 at 8:53 PM, Omindu Rathnaweera <[email protected]> wrote:
> Hi Biruntha,
>
> Are there any plans to update the connector with the new APIs ?
>
> Thanks,
> Omindu.
>
> On Tue, Jul 24, 2018 at 11:04 AM Biruntha Gnaneswaran <[email protected]>
> wrote:
>
>> Hi All,
>>
>> We are planning to deprecate Mepin authenticator[1] from the store[2]. In
>> our Mepin authenticator, we are using the Mepin simple_api endpoint [3] to
>> authenticate and retrieve user information. Since this endpoint has been
>> deprecated recently and giving 502 Bad Gateway error, we are planning to
>> deprecate.
>>
>> Please let us know if there are any concerns.
>>
>> [1] https://docs.wso2.com/display/ISCONNECTORS/MePIN+Authenticator
>> [2] https://store.wso2.com/store/assets/isconnector/details/
>> 00902cc7-5efc-4b8f-aae7-930e999f8058
>> [3] https://api.mepin.com/simple_api/
>>
>> Thanks,
>> --
>> Biruntha
>>
>> Software Engineer
>> WSO2
>> Email: [email protected]
>> LinkedIn: https://lk.linkedin.com/in/biruntha
>> Mobile : +94773718986
>>
>
>
> --
> Omindu Rathnaweera
> Senior Software Engineer, WSO2 Inc.
> Mobile: +94 771 197 211
>
--
Biruntha
Software Engineer
WSO2
Email: [email protected]
LinkedIn: https://lk.linkedin.com/in/biruntha
Mobile : +94773718986
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
