Good Day Fellow Foundryans, I'd like to share and gather feedback on proposed scope of the next major release of cf-deployment. This Google doc describes the high-level

Hi Dario, I completely understand the sentiment. I did not mean to talk about deprecation in this fashion. Our intention is to do a survey with the CF community and understand the usage of UAA

Seems that discussion has died down on this.... At this point, it appears that consensus is around not adding Erini yet and reassessing when the project is further along. We can certainly make changes

I agree that it would be worthwhile for the community to hear more of the thought process from Sree or others in the project team. Would the project be open to PR's from interested parties (like

Hi, everyone, Pivotal is nominating Jonathan Sirlin for the CF Networking Project Lead in the Application Runtime PMC. Jonathan has been working as a product manager on the CF Networking team for the

Hi, everyone, Preethi Varambally, the Project Lead for the CF Networking team within the Application Runtime PMC, is stepping down from the project to join the CF Infrastructure team. We thank her for

Hi Deepak, You can use something like service broker for credhub for CUPS https://github.com/cloudfoundry/secure-credentials-broker Thanks Ronak

Hi Do we have any solution for issue https://github.com/cloudfoundry/docs-services/issues/156 Thanks Deepak Lokhande +91 955 269 7122

Hi Sree, This is disappointing news. There are members of the community that have come to rely on UAA as an alternative to deploying burdensome enterprise solutions. Would it be possible for you to

Hi Ryan, Best would be to fork and add the needed features for password policy. UAA will continue to support all the federation use cases and act as an OAuth2 server Thanks, Sree

Thanks for the explanation, Sree. Do you have additional information about these plans? My organization likes using open source software for user/password, OAuth client, SSO, etc data so we'd like

We are planning to deprecate the use of internal use store and any other features around password policy. Internal User Store will be for dev only use. Because of this, we are not working on

Hi, thanks I understand that. But we'd like to prevent the last 3 (or 8 or 0) passwords being used. Is this a feature others would be interested in?

Hi Ryan, This is intended behavior to prevent reuse of password essentially a password history check Thanks, Sree

Currently during a change password operation, UAA has a hard coded check preventing the use of the most recent password. Has there been any work on customizing this behavior to preventing the last X

Hey all, It is that time of the year -- register for Summit North America 2019! For those that don't know, we are headed to Philadelphia in April (2-4), 2019! Contributors (those that have

+1. Our main intent certainly was to avoidcertification FUD in case we accomplish a "mature" Eirini inthe first half or 2019. To me ammeding the requirements with a mid-termupdate does address this,

I think that there is AllowSyscall list inside seccomp.go of guardian as a default. I just wanted to provide this AllowSyscall list as an option each time when I push an app. That's too bad to hear

That sounds reasonable. I was going to add some "pending feature parity and passing CATs" language in the proposed change, but ammeding the requirements with a mid-term update would probably satisfy

Correction. Looks like there is an experiemental zdt restart command also: "cf v3-zdt-restart" Mike