where the Roles class store the roles that he creates, what is the type of role providers that support this class?
is it SqlRoleProvider?
here I think you will find the answer to your question.
read this section in the article:
Using SqlRoleProvider
If you want to store roles in SQL Server, you
use the SqlRoleProvider. By default, roles are stored in a database
named Aspnetdb in a SQL Express database instance in the \app_data
folder beneath your application's virtual directory root folder. You
can also configure the SqlRoleProvider to use a local or remote
instance of SQL Server.
Related
We have an on-prem server which is also in our backup solution.
We were trying to create a new delegated LDAP permission for a different team by using the Add Directory option within User Directories in the Administration. We were able to create the directory but when we deleted it post the testing, the configuration made in the original directory were removed, specifically from the ldap.group.filter
Now we are trying to retrieve the old config file however I dont know the location where it is stored. Is it stored on the server or does it also reside in the DB? Is there a way to restore it without restoring the entire server?
I am on Apex 5.1 in a hosted environment and have an application that uses a custom LDAP authentication function. It works fine when the application is running on the Production schema. I now wanted to make some changes to the schema and application, so our hosting vendor added a 'DEV' schema on same instance with exactly the same data and objects as PROD and I then exported the application and used the DEV schema as the parsing schema when I imported it back to same Workspace so I could make changes to the application without touching prod data. This set up works fine when I use the Application Express authentication and go ahead and make changes to the DEV schema and to the application, but when I try to test my changes using the custom LDAP authentication, I am getting Invalid Session thrown by DBMS_LDAP. Since both schemas are on the same oracle server, I assumed that the same LDAP function that works in PROD schema should work with the DEV schema. Looking at the custom LDAP function, there is no reference to schema owner so what am I missing? I would have assumed identical functions should function identically against the same Oracle server even though coming from 2 different schemas. Does my hosting vendor need to make sure ACLs for both schemas (PROD and DEV) are identical??
Thanks,
Pat
My guess was correct. ACLs were not set identical for both schemas. Once ACLs were adjusted, LDAP worked as expected.
I want to assigned basic read-only permissions for a PostgreSQL database role that must access from an Application server like Glassfish.
For a production system, you can use the configuration described in this post :
What GRANT USAGE ON SCHEMA exactly do?
Is it possible in any of the existing LDAP servers to edit a schema in one of the editors available? Like JXplorer, Apache Directory Studio, LDAP Admin?
I tried with OpenLDAP and all of the above tools (I run the server with -F option) but it looks like it's not possible to modify schema - add new attributes, add descriptions etc.
I would be grateful if any of you have some experience with this.
Cheers
Some LDAP servers allow (authorized users) to change the schema by sending LDAP modify operation affecting the so-called subschema subentry directly, but not OpenLDAP.
In OpenLDAP you have two possible configuration methods:
Static file configuration usually with schema files being simply included (aka slapd.conf) which requires slapd to be restarted to make configuration changes effective
Dynamic configuration backend back-config (aka cn=config) for which you can also define ACLs restricting access to your LDAP admins
The dynamic configuration method allows to tweak the schema via LDAP making it effective without server-restart. But you have to modify the multiple LDAP entries in sub-tree cn=schema,cn=config which you can do with any generic LDAP client.
Since schema descriptions usually reference other schema descriptions the order is important. Standard LDAP does not know about order of entries beneath an entry or order of attribute values. Therefore OpenLDAP implements an extension specified in draft-chu-ldap-xordered.
Added RavenDB add-on to AppHarbor app.
It seems that creating databases is disabled in the RavenDB admin.
Why?
You should already have had one created for you, the connectionstring is injected into your configuration file with the name RavenDB. Details here: http://support.appharbor.com/kb/add-ons/using-ravendb-and-ravenhq
I believe they use the multi-tenant support to separate each customer, so you have a single database created for you when you add the addon.