Skip to the content
IPification - Mobile authentication solutions
Menu
Menu
Have a Question?
Search
06. Implementation Requirements
01. Does VPN require implementation?
02. What is the minimum version of CentOS that can be supported?
03. Does IPification require a load-balancing node to handle this?
04. What information does IPification require for implementation?
05. Do you support onsite implementation?
06. What is the capacity of GMiD™Box?
07. What are the network requirements?
08. How many IP addresses of IPification Auth nodes have (Identity Provider - IdP)?
09. Is your solution compatible with IPv6?
10. GGSN/PGW/AAA supports sending Acct messages in 3 modes (synchronous, asynchronous, periodic mode). Which mode does IPification prefer?
11. Is it possible to use 4 sets of [4xCPU] servers instead of 2 sets of [8xCPU] servers?
12. Is a GMiD™Box able to install on bare metal instead?
13. If incoming traffic is higher than memory availability, what will happen? How GMiD box handle the overflow traffic? Is there any impact on the customer?
14. Is there any other DB option besides Redis DB?
15. *We prefer to see a simple TXT NAT log instead of this fancy table, the format how CGN sends via Syslog. Can you share a plain TXT log? (See original)
16. *But in Test cases document, in “expected results” of test cases 1 – 4, there are “SubID, MSISDN, MobileID” values. (Both in case that MSISDN has been collected and not collect on the Service Provider side)
17. *So does it mean that all these 3 values (“SubID, MSISDN, MobileID'') will be responded back to the IPification Auth node (IdP)?
18. *Please help explain, what is “SubID” used for? Who generates this value?
19. *In test case 1 and 3, in which scenario does “Plain MSISDN” have to return in response? Does “Plain MSISDN” also return in response for the Production stage?
20. *In case that MSISDN has to be returned a response, can we strictly allow only “Hashed MSISDN” to be returned?
21. *In test case ID 2: It is the case where MSISDN is returned in the response. Does this case just for MNO purposes? Will this case be applied commercially with any service provider? (We have a concern on return MSISDN value outside)
22. *Could you explain to us some concrete use cases: Authentication within an app, the operating system, the browser…
23. *Do you have a kind of "white paper" for seamless login via mobile phone?
24. *SIM change/device change notification: During our PPT to clients we usually tell them that our solution creates a unique mobile id based on the golden triangle (mentioned below) and if any of these parameters are changed, our solution will capture and notify them. whereas in reality that's not the case, our solution does not capture Sim change in real-time, they have to send us authentication requests specifically. Is that correct? Also if they change devices then our solution will create a new mobile id & share in real-time as they will reinstall the mobile app. Correct? Also what happens if a user simply un-installs the App & re-installs again, do we create a user id again, does that count as a new authentication?
25. If the client agrees to authenticate their live users once in say 15 days, how will we authenticate all of their live users because each user would be live on different days? I want to understand how exactly we will manage this?
26. *SIM Swap and Auth APIs can be called separately?
27. *SIM Swap and Auth APIs are separate services and will be charged as separate services?
28. How does Mobile Connect participate?
29. How is the access for non-mobile devices (laptop)
30. What are the infrastructure requirements for the GMID to ensure 99.99% availability?
31. What means "One OIDC Client API for SP"?
32. What is the coverage of the platform in mobile equipment if the operation is generated by only one telco (MNO) operating in the country? or should the application (IPification) be available on all telcos (MNOs)?
33. Are there any additional costs to the end-user in operating costs of financial insurance on this platform?
34. How are resolved when there is no Telco Coverage in 4G or 5G, when a transfer is being performed.
Show all articles (19)
Collapse Articles
You are here:
Main
06. Implementation Requirements
Category - 06. Implementation Requirements
Articles
01. Does VPN require implementation?
02. What is the minimum version of CentOS that can be supported?
03. Does IPification require a load-balancing node to handle this?
04. What information does IPification require for implementation?
05. Do you support onsite implementation?
06. What is the capacity of GMiD™Box?
07. What are the network requirements?
08. How many IP addresses of IPification Auth nodes have (Identity Provider - IdP)?
09. Is your solution compatible with IPv6?
10. GGSN/PGW/AAA supports sending Acct messages in 3 modes (synchronous, asynchronous, periodic mode). Which mode does IPification prefer?
11. Is it possible to use 4 sets of [4xCPU] servers instead of 2 sets of [8xCPU] servers?
12. Is a GMiD™Box able to install on bare metal instead?
13. If incoming traffic is higher than memory availability, what will happen? How GMiD box handle the overflow traffic? Is there any impact on the customer?
14. Is there any other DB option besides Redis DB?
15. *We prefer to see a simple TXT NAT log instead of this fancy table, the format how CGN sends via Syslog. Can you share a plain TXT log? (See original)
16. *But in Test cases document, in “expected results” of test cases 1 – 4, there are “SubID, MSISDN, MobileID” values. (Both in case that MSISDN has been collected and not collect on the Service Provider side)
17. *So does it mean that all these 3 values (“SubID, MSISDN, MobileID'') will be responded back to the IPification Auth node (IdP)?
18. *Please help explain, what is “SubID” used for? Who generates this value?
19. *In test case 1 and 3, in which scenario does “Plain MSISDN” have to return in response? Does “Plain MSISDN” also return in response for the Production stage?
20. *In case that MSISDN has to be returned a response, can we strictly allow only “Hashed MSISDN” to be returned?
21. *In test case ID 2: It is the case where MSISDN is returned in the response. Does this case just for MNO purposes? Will this case be applied commercially with any service provider? (We have a concern on return MSISDN value outside)
22. *Could you explain to us some concrete use cases: Authentication within an app, the operating system, the browser…
23. *Do you have a kind of "white paper" for seamless login via mobile phone?
24. *SIM change/device change notification: During our PPT to clients we usually tell them that our solution creates a unique mobile id based on the golden triangle (mentioned below) and if any of these parameters are changed, our solution will capture and notify them. whereas in reality that's not the case, our solution does not capture Sim change in real-time, they have to send us authentication requests specifically. Is that correct? Also if they change devices then our solution will create a new mobile id & share in real-time as they will reinstall the mobile app. Correct? Also what happens if a user simply un-installs the App & re-installs again, do we create a user id again, does that count as a new authentication?
25. If the client agrees to authenticate their live users once in say 15 days, how will we authenticate all of their live users because each user would be live on different days? I want to understand how exactly we will manage this?
26. *SIM Swap and Auth APIs can be called separately?
27. *SIM Swap and Auth APIs are separate services and will be charged as separate services?
28. How does Mobile Connect participate?
29. How is the access for non-mobile devices (laptop)
30. What are the infrastructure requirements for the GMID to ensure 99.99% availability?
31. What means "One OIDC Client API for SP"?
32. What is the coverage of the platform in mobile equipment if the operation is generated by only one telco (MNO) operating in the country? or should the application (IPification) be available on all telcos (MNOs)?
33. Are there any additional costs to the end-user in operating costs of financial insurance on this platform?
34. How are resolved when there is no Telco Coverage in 4G or 5G, when a transfer is being performed.
+ 26 Articles
Show all articles
IPification - Mobile authentication solutionsIPification - Mobile authentication solutions