#acumos-meeting: Architecture Committee

Meeting summary

1. Agenda, single sign on, bi-directional, AiF 360 has a plugin and use cases (IBM (Romeo), ATT, TechM), Secure RTU. Portal team wants to discuss super admin development. (farheen_att, 14:07:06)
   
2. Single Sign On Integration (farheen_att, 14:08:39)
   1. there is a space in wiki.acumos.org. Ai4u can provide development resources to develop this but we will need guidance. Ai4u or Nokia have their own instance and have their own directory identity server used for single sign on. Oauth2 with openid. Uses ws02 which uses oauth2 with open id just like acumos. It would be great to have just a (farheen_att, 14:11:09)
   2. if new users must be added they should be added to the external identity server if the internal identity server is disabled. Nokia wants to disable the cloud deployment because it leaves a back door open. An Azure token out of the box would be nice. (farheen_att, 14:12:22)
   3. proposal to make an epic to make SSO configurable. We need someone from architecture or portal to create the user stories for us so we know where to do the implementation and not break anything. We will bring it in a secure way to the current code base. There are in the sign up dialogue for Facebook, Google, ... I is not developed. (farheen_att, 14:13:51)
   4. Manoop - Agree the requirement is an important one that will benefit the entire community. We agree on this requirement. (farheen_att, 14:14:59)
   5. the "Deploy to cloud" comment on the wiki page should be removed. (farheen_att, 14:15:48)
   6. Manoop - In Acumos-LF we are able to configure with the LF ID server. That is the user account. (farheen_att, 14:17:06)
   7. for internal AT&T acumos enforced a cookie style authentication. (farheen_att, 14:18:19)
   8. Vasu - we deploy working source code. It is configurable on Acumos-LF. (farheen_att, 14:19:56)
   9. Nat - March 2018 we disabled the social logins. (farheen_att, 14:21:10)
   10. resource usage may not be related to AiO installation. CPU disc space etc. (farheen_att, 14:22:11)
   11. Optimization (farheen_att, 14:22:21)
   12. one year ago we had a challenge for ML modelers and we analyzed and found the minimum requirements to install. (farheen_att, 14:23:14)
   13. we can take it under consideration with platform hardening. (farheen_att, 14:23:33)
   14. Nat - that hardware recommendation is posted in the documentation. (farheen_att, 14:24:01)
   15. Manoop - There will be an installation guide that should not be as manual. We will move away from one click deployment. (farheen_att, 14:25:14)
   16. Priya We should verify if this is plugable with any or only specific Identity servers. (farheen_att, 14:25:34)
   17. Manoop- it works with oauth2 and google logins work. (farheen_att, 14:25:53)
   18. Nat - we don't have to implement new, Rajesh and Vasu contact Martin. (farheen_att, 14:27:50)
   
   
3. Bi-directional Federation Wenting. (farheen_att, 14:28:12)
   1. Bi-directional Communication (farheen_att, 14:28:33)
   2. bi-directional communication between supplier and subscriber. (farheen_att, 14:29:10)
   3. recorded demo (farheen_att, 14:29:48)

Action items

1. (none)

People present (lines said)

1. farheen_att (27)
2. collabot` (3)