MON - 21st NOV 2016

[peeyush-tm]

Reference for the discussion

• Ref: #5

Monday's Discussion

• How to enable
  • widgets on a terminal
    • who are you
    • whom to meet
    • action (check in / check out)
    • scanner
  • edit the widget processes
    • onboard member with MFA
    • onboard member without MFA
  • dynamic widgets / instant apps on user app
    • on mobile
    • on web
    • on user app
  • difference between ADMIN PANEL & MEMBER PANEL
  • How to manage permissions - Admin / Owner / Member
  • How to unify user's membership data

Veris is ID for EVERYTHING EVERYTHING is literally EVERYTHING Veris Platform checks ACCESS of ID on EVERYTHING

The use cases for the interactions or context are not fitting in well with the platform we want to build.

Let's sit again, with precise questions, at 7:00 PM today (for max 1 hour).

[peeyush-tm]

@veris-neerajdhiman @veris-ankitpopli @veris-amoghbanta - Please update, individually, all the points if the discussion. I would like to correct-re-correct till we get things right.

• Veris platform has a base of ID, because literally ID is everywhere and ID is everything
  • wild examples
    • laptop (id = mac address)
    • router (id = ip address)
  • useful examples
    • google plus
      • personal
      • organizational
    • veris id
      • organizational

We enable use cases for ID & interaction of ID with Everything We want to create CONTEXT of the interaction and record that.

Instant Apps are just a Context of interaction between User (member) & Organization.

Please update your discussion points (all of them, even the smallest ones) here.

[peeyush-tm]

@veris-neerajdhiman @veris-ankitpopli @veris-abhinavanand @veris-amoghbanta

Can we beat the giants ? I believe we can..

V- Win.pptx

[veris-neerajdhiman]

• How we are different from Okta and Auth0 ?

  • Veris is a IAM, mainly we concentrate on Ids or you can say we are a Id provider but we also manage Resources and their Access.
  • What actor can perform WHAT on which Resource will be manage by Veris.
  • Hew we will identify any Resource , So basically every Resource will be provided an Id so he needs to register with Veris First.
  • we don't stop Here :)
  • We are also providing our users a RunTime , where they can run any process or event according to thier requirement or user case (these will be handled by widgets).

• Problems or Questions or Doubts :

  • How to identify RunTime ? - Solved, using name spaces.
  • Identify System and public Resources.
  • Are Id scopes/permissions and Access level permissions are different ?
  • Where to keep Trust Scores are they related to User ? - Solved,. (Trust Score related to users and will be kept with Id server)
  • AS per our discussions, Widgets are independent entities and they work in their own scope. What if user wants an event which Require two or widgets to communicate with each other, Or whether to resolve a widget or not is depends on result of another widget

• The main focus should be to treat each process, event as its own and where it needs to draw a line (make a system assumption or rule), we should.

• Where to start ?

  • Start From organization , create a single simple widget (with some assumptions) and after that start removing assumption one by one, put new use cases and see how things flow, interact with each other, are they breaking any concept that we have discussed.
  • Assumptions :
    • Don't concentrate on id for now.
    • Assume there is only One organisation (which is valid already have one owner who can perform every possible task a organisation can perform in future).
    • Don't concentrate on scopes/permissions
    • Add member to Organisation (using forms , no external connector are needed).
    • Create one Widget for logbook and start logging events for members and see how things work.

• Most important :

  • Believe in yourself.

[veris-abhinavanand]

terminal v2.4.3 ready for release. Release notes fc772fb chore: bump app version to 22(2.4.3) :arrow_up: 1ea9bf9 chore: upgrade android sdk version from 24 to 25 :arrow_up: 817c6ab chore: upgrade google phone number lib :arrow_up: 6e283fc feat: set print quality to HIGH_RESOLUTION 211f9ec fix: resolve issue where printer ip address is empty :bug: f8fc947 chore: upgrade printer sdk to 3.0.5 7ca6273 fix: improve performance of auto complete meeting with :bug:

[veris-amoghbanta]

[veris-amoghbanta]

[peeyush-tm]

What is Veris's USP (Unique Selling Point) ?

• Veris provides an Organization a functionality to serve their members or non-members with INSTANT APPS (that runs on Veris Runtime)
• Veris provides TRUST SCORE to EVERYTHING, based on the Context of Interaction between two or more EVERYTHING
• That means => Veris is ID for EVERYTHING

What is Context of Interaction? What is ID for EVERYTHING?

• a User (ID: user), goes to a Bank (ID: org) and fills a Form (ID: widget), on a Veris Runtime Terminal (ID: terminal)
• Context of Interactions between these IDs
  • Why User filled the Form ? (apply for loan)
  • What Will bank do with the Form? (provide loan)
  • Who will be affected by the end result of the interaction? (bank & user)
  • This means that CONTEXT is LOAN
    • the result will be judged by user => positive or negative
    • the result will be judged by bank => positive or negative
    • the result will be marked by the user & the bank => weighted average of the judgment by the user and the bank
    • for the CONTEXT => Bank will have a score of (+10) and User will have a score of (+10)
    • next time, for the same CONTEXT, User will get a Loan, without even filling the Form, because Bank has set a threshold to provide a Load to (ID: user) >= +10

OMG??!! Rightly SO 😄

We at Veris, wants the platform to be so that, any ID can INTERACT/ACCESS with any ID, under a CONTEXT. For successful INTERACTIONs, the IDs get SCORED, within the CONTEXT, a perfect SCORE ensures that ACCESS is always TRUSTED and SEAMLESS.

A World without Boundaries ! (if you have a good score 😄 😄 😄 )