claims

I have this problem when using SAML SSO authentication. I have successfully set up WSO2IS 5.0.0 Identity server, I also succeeded setting up (at least I hope so) secondary user store. I used JDBCUserStoreManager implementation. I have set this store as DOMAIN. This user store works nice, at least I think it does. Because it is storing user attributes into its tables (USER_ATTRIBUTES) and those attributes are read by WSO2IS administration ... https://localhost:9443/carbon/userprofile/edit.jsp?username=DOMAIN/demo_jbu&profile=default&fromUserMgt=true Users are identified as DOMAIN\username so

On my Kubernetes cluster on GKE, I have the following persistent volume claims (PVCs): kind: PersistentVolumeClaim apiVersion: v1 metadata: name: registry spec: accessModes: - ReadWriteOnce resources: requests: storage: 100Gi and: kind: PersistentVolumeClaim apiVersion: v1 metadata: name: postgresql-blobs spec: accessModes: - ReadWriteOnce resources: requests: storage: 100Gi Amongst others, I have the following persistent volume defined: kind: PersistentVolume apiVersion: v1 metadata: name: pv0003 spec: capacity: storage: 100Gi accessModes: - ReadWriteOnce - ReadOnlyMany gcePersistentDisk:

I'm trying to understand what I need to develop a framework using WCF, Claims and ADFS 3.0. The internal users will authenticate against Active Directory, External User authenticate against SQL Server table and the authorization is stored in database tables implementing groups and permission. I am creating a API using WCF not Web Api or OWIN. I'm not interested in using Identity Server or 3rd party products, I just want to know how I create a Custom Security Token Service to read from my membership table and set claims via my Groups and Permissions table. I can find no information on any of