I want to get the bellow Azure Active directory group setting value from Graph API. Could you please let me know how i will get it using Graph API?
$directorySetting["AllowToAddGuests"]
As of now i have tried with this, But this is not suitable for my requirement. So i need to get actual value from this setting $directorySetting["AllowToAddGuests"]
https://graph.microsoft.com/beta/groups/{id}?$select=allowExternalSenders
You can find this from the Group Settings collection (/groups/{id}/settings):
Group settings control behaviors such as blocked word lists for group display names or whether guest users are allowed to be group owners.
note that this is a nullable collection and many (if not most) groups will return an empty array
I'm assigning groupLifecyclePolicy to thousands of O365 groups via my webapp and I need a way to retrieve the groups that have the groupLifecyclePolicy assigned without querying every single group individually.
Unfortunately the groupLifecyclePolicy does not have a "List groups with specified groupLifecyclePolicy" method.
Is there any way to create a filter that filters on this?
I tried
'https://graph.microsoft.com/beta/groups/5e879c76-cd26-4238-a94f-ba0ade56a659?select=id,displayName,groupLifecyclePolicies'
but only got the 2 other attributes. I think this means, that the attribute is a lookup elsewhere.
Does anyone know of a way to apply a filter similar to (pseudocode):
'https://graph.microsoft.com/v1.0/groups?$filter=contains(groupLifecyclePolicies)'
or any other way that does not involve calling:
'https://graph.microsoft.com/beta/groups/<id>/groupLifecyclePolicies'
for all groups?
Unfortunaly it is not possible. The only way, indeed is to separate it in multiple requests.
Get all group id`s:
https://graph.microsoft.com/v1.0/groups?$select=id
Get policy property:
https://graph.microsoft.com/v1.0/groups/{id}/groupLifecyclePolicies
Make sure to add Retry-After header to avoid throttling(https://learn.microsoft.com/en-us/graph/throttling)
I have an nFeed plugin on my Jira instance that I'm trying to learn to use. I have a select list in my create screen and I have it configured to JNDI. When I go to my select list, it has 3 options (how many rows in my table), but they're all blank.
Here is my query
SELECT p.PRODUCT_NAME, p.PRODUCT_ID FROM NIRD_Product_Groups p
and my key is 0
I have native filter checked and the display template is {1}
anyone hae an ideas what the problem could be?
It looks like probelm with your SQL query.
- Have you tried to enable the Debug mode of this nFeed field to figure out if ther is any error raised ?
- What type of database are you pulling data from ? Depending on its type you probably need to put double quotes around your attribute and table name in your query.
- You set the key as 0, which refers to the PRODUCT_NAME attribute. Would not it be safer to set the key as PRODUCT_ID ? This sounds more accurate to me.
- Have you tried to test this configuration on a different web browser ?
If you need further help, Valiantys is providing free support on its plugin here : https://jira.valiantys.com
I want to generate an IDOC file to make shop orders availabe to the R/3 SAP System. My question is concerning BELNR in E2EDK01. As we dont have the possibility to use Webservices and BAPI, we only make the data available via files.
Actual questions are:
Do i yet need a [BELNR] in the IDOC file?
If yes, where to get this [BELNR] from?
E2EDK01-BELNR is the order number of the ordering party, normally it is not needed, but useful.
Example:
The customer sends an order and is unsure if the order received you. So he sends the order again. Now you have two similar orders. You can't know, if there are two similar orders or if you have two idocs for the same order.
If E2EDK01-BELNR is filled with the order number of the customer system, you can decide how to proceed (e.g. ignore the 2nd idoc).
If I understand your question correct, you create the order out of your shop system. You could offer an (optional) field like 'Your order number' and use this. If the same order number (per customer) is used again you can make a warning ("Order X is already ordered").
If you don't want this field you could use the session id to identify double postings.
In our LDAP directory, we have users, who are mapped to groups. Those groups may be mapped to other groups. For example:
cn=group1,cn=groups,dc=example,dc=com
uniquemember cn=user1,cn=user,dc=example,dc=com
cn=group2,cn=groups,dc=example,dc=com
uniquemember cn=user2,cn=user,dc=example,dc=com
uniquemember cn=group1,cn=user,dc=example,dc=com
So User1 belongs to Group1, but User2 belongs to Group2, which in turn belongs to Group1
Within Grails, User1 has authority to Group1, but User2 only has authority to Group2. From what I've seen, there is no way to cause it to recursively look at the tree. Realistically, I probably only need a 2 level hierarchy, but even that doesn't seem to work.
I'm attempting to work through the Custom UserDetailsContextManager to see if I can iterate over the initial results and re-query LDAP by group, but I thought I'd see if there was an easier/better way.
You probably already saw this, but this is from the documentation:
// If you don't want to support group membership recursion (groups in groups), then use the following setting
// grails.plugins.springsecurity.ldap.authorities.groupSearchFilter = 'member={0}' // Active Directory specific
// If you wish to support groups with group as members (recursive groups), use the following
grails.plugins.springsecurity.ldap.authorities.groupSearchFilter = '(member:1.2.840.113556.1.4.1941:={0})' // Active Directory specific
http://grails-plugins.github.com/grails-spring-security-ldap/docs/manual/guide/2.%20Usage.html
Oracle OID has a product-specific extension for traversing the hierarchy, known as CONNECT_BY, which has LDAP OID 2.16.840.1.113894.1.8.3 . You can add this as a request control to ask the server to connect/follow hierarchies according to an attribute you specify. This can be done using both a Java LDAP client program, or using something like OpenLDAP ldapsearch, although the set-up is a little tricky.
If you want to use Java to follow the hierarchy, this page contains a sample program which shows how to setup the required javax.naming.ldap.Control implementation class, in this case named ConnectByControl.
You can also perform this sort of hierarchical search using ldapsearch, but it requires some preparation and implied understanding of the required control value, as the value is concatenated then base64-encoded. The value is in two-parts - the follow-me depth (0=unlimited), followed by the connect-by attribute name (in this case, uniquemember is the desired name). Set the baseDN in your query to the entry where you want to start the hierarchical search.
ldapsearch -H ldap://myoidserver.mycompany.com:389 -e 2.16.840.1.113894.1.8.3=MBECAQAEDHVuaXF1ZW1lbWJlcg== -b cn=some_group_containing_groups_nested_by_uniquemember,cn=some_groups,dc=mycompany,dc=com "(objectClass=*)" dn uniquemember
The -e 2.16.840.1.113894.1.8.3= adds the CONNECT_BY request control. The value, MBECAQAEDHVuaXF1ZW1lbWJlcg==, is ASN.1 BER-encoded then base64-encoded value 0uniquemember, for the depth and attribute-name mentioned above. This will print first the dn for cn=some_group_containing_groups_nested_by_uniquemember,... and its direct (user) uniquemembers, then each uniquemember will be "connected" or followed. If that entry itself has a set of uniquemember, i.e. it is a nested group, the process will continue until leaf/user entries are reached that have no nested uniquemembers.