We need to know the domain so we can white list it - buildfire

The developer of our plugin needs to know the source and destination of the login call so that they can white list the domains. How can we get this information?

Related

How to rollout to all gmail users changing a sender's emails categorisation from the Promotions tab to the Primary tab in the default gmail layout?

Our company uses gsuite, and the standard gmail default layout has the tabs for Primary, Promotions, etc. It can be changed (I perfer to) but some keep the default layout.
Our mailing tool with email editor etc is external, and so has a different domain. It gets flagged as Promotions. This is an issue for all those with the default layout as they have to keep looking through Promotions for internal news.
How does an admin / IT department change where a sepcific sender's emails are categorised in these tabs in google's business suite for all users?
Things we've looked at:
I asked our IT department, and they have not found an easy setting or way to control where domains / senders are categorised.
We added the IP ranges our mailing tool sends from, however this only stops the emails being marked as Spam / suspicious. Good to have, but not a solution to tabs.
There is plenty of ways to control it for your personal inbox, and move it manually or set up rules etc as an end user. However we can't expect everytone to do this, we need a way of the admin being able to make the change and roll it out to everyone in the business.
For a seperate issue regarding rolling out email signatures to all users automatically in their inbox settings, there was a solution but required using their API and delving in code rather than an admin setting. If there's a way to somehow do it with that we're happy to explore.
Apparently this is easy to do in other ecosystems such as Microsoft, but we are yet to find an easy way to do this in Google's system. Any ideas?

How can I add Environment related text to Azure AD login page

As shown in the image I want the text to appear at top relative to environment used:
I viewed the Company Branding option but there I only saw options for background image and logo .
As for now I don't have credentials to login. Its just R&D work given to me to determine feasibility. I am sure there would be some way, but that I am not getting it. That's why I posted this to Stack Overflow.
The Company branding will be reflected to the entire tenant level(reflected on all application).
You can't differentiate by the environment as it will be show for all application while sign-in.
Using company branding you and set
The large illustration and/or its background color
The banner logo
You can also add text to this area.
Please go through the document for more understanding

Redirect based on browser language

Here is an issue we are having with our website developed in XPages which is accessible in several regions and languages. Based on the browser language we are able to determine which header to display at the top of web page. Our content is then displayed for that language in that region. Content displayed is from individual documents in a Domino database and there is one for each language so the user can see language friendly data. Some documents are only for a particular Region/Language and not translated for other regions due to availability of the product.
The issue is when someone clicks on a link (ie via social media let's say) like https://www.cascorp.com/americas/en/reach-forks they go to the americas English version but the header and menu items are displayed in the browser language and content is displayed in the English language. Server Redirect rules won't work in this case. It would be nice to be able to redirect them to https://www.cascorp.com/eme/en/reach-forks and have a page that comes up stating that the product is not available for that region. Is there a way I can dynamically change the address bar to redirect them to a different document by replacing the region part of the address? This way we can have a document for that region/language stating that the product is not available in their region.
You can use context.redirectToPage(nameOfXpage) to redirect based on your language logic.
For a partner of mine, www.the-academy.nl, we decided to abandon Server Redirect rules completely, so we installed Apache as a reverse proxy server. It gives you full control over all links in and out if you want, and we managed to remove all visible references to the web database. Apache can be installed on the same system as Domino (easiest on Linux). It might be a bumpy ride, but it's worth it.

Check a Liferay portal in Quantcast, Alexa and others

I have a portal in Internet, and I would like to register it in sites like Alexa, Quantcast and other similar sites for ranking and web analyzes.
However, in most of the cases I have to put an HTML file inside the portal, however I do not know how, because all uploaded files are web content in Liferay, and the address is not the address that those sites are going to look for.
In other cases, I have to put an extra meta-data tag, but the only one that I can modify is the keywords meta-tag.
I do not know how to put a file specifically in the portal or add a special meta tag in the head section.
Thanks for the assistance.
You can add those in theme of yours. Check out portal-normal.vm to add meta tags in the head section. And you can create a separate footer.vm if you want to include any javascript snippet.

Hiding Distribution lists from Sharepoint Membership List

On the "My site" feature of Sharepoint there is a "memberships" Web part that shows the distribution list that the user is a member of.
This is picking up several groups that we would rather not be shown e.g. some that have been set up for administrative purposes only.
Is there any way to control which groups are shown; ideally this would be using another AD group and setting that only members of this group are shown.
I'm fairly sure this won't be possible without a custom web part that is deployed instead of the official part. The reason the Exchange solution doesn't work is because it's going the wrong way (from group to member instead of member to group).
To deploy it you can look at feature stapling... you would need to update the existing sites as well.
This is not an easy answer. I don't believe there is an easy answer.
The best solution would be to set a Deny Access Right for the distribution lists in Active Directory; follow these steps:
1) Open Active Directory Users & Computers as an admin (any user with access to creating groups and modify distribution list security settings).
2) Go to the View menu and make sure that there's a check-box next to Advanced Features.
Create a new security group in Active Directory (call it HideFromSharePoint or something) and add the SharePoint Content Access account (in my case DOMAIN\sa_spcontent) to that group (has to match the account used in step 4).
3) For all of the distribution lists that you don't want to show up in SharePoint do the following:
3a) Open the distribution list and select the Security tab (Advanced Features must be checked for this tab to be shown).
3b) Click on Add and type in the name of the security group that you created in step 3 (HideFromSharePoint); click Check Names and click Ok.
3c) Under Permissions for HideFromSharePoint; check the Deny box next to Read (it's set to Allow by default) and click Ok and Ok again at the prompt.
You've just denied any members of the HideFromSharePoint group read access to the distribution list.
4) Go to SharePoint Central Administration; SharedServices1; User Profiles and Properties; Configure Profile Import and under Specify Account enter the credentials of the account that you added to the HideFromSharePoint-group in step 3. (For some reason if you leave this to using the Default Content Access account SharePoint will use some other account to access Active Directory and thereby being allowed access to the distribution lists. You could experiment with adding other SharePoint service accounts to the HideFromSharePoint group but I think it's safer to specify an account explicitly so that you know which account is accessing AD and importing the data.) Also make sure the "Import Connection" for your Active Directory is set to "Use Default Account" (thereby "inheriting" the account used for Profile Imports).
5) Go to SharePoint Central Administration; SharedServices1; User Profiles and Properties and click on Start full import. (You can't do an incremental import because nothing has changed for the users in terms of group membership; it's just the access rights that have changed.) After completion of the full import (click Refresh until "Import time:" says "Started full import at 11/25/2009 ##:## AM - Ended import at 11/25/2009 ##:## AM")
The distribution lists should now no longer show up under Memberships.
A couple of things to note:
You have to set the Deny Access Right explicitly and individually on all of the distribution lists that you don't want showing up in SharePoint. That's because the special AD-group "Authenticated Users" has read access to every object in the directory by default and explicit Allow Access Rights trump Deny Access Rights set (for example) at the organizational unit level.
While you could skip the step of setting up the HideFromSharePoint-group and set the Deny Access Right directory for the SharePoint Content Access account Active Directory administration best practices is to use a group when configuring security permissions. (Then you can add additional members to that group and have those denied read access too.)
You might have to wait a while (5+ minutes or so) between setting the the Deny Access Rights for the changes to replicate to all of you domain controllers. Otherwise the import might read from a domain controller where the Deny hasn't yet come into effect.
Be careful adding any other accounts to the HideFromSharePoint-group because this might break your distribution lists. For example; if Exchange can't read the groups mail won't work. As long as you just add the SharePoint Content Access Account you're safe.
Also (and this has nothing to do with SharePoint or the solution above) be aware that any user in your domain can fire up ADUC or a LDAP tool and see the members of your distribution lists that way. If you have anything "Top Secret" you need to experiment further with setting access controls in Active Directory.
I assume that your "memberships" web part is using the SharePoint people picker functionality internally.
If that's the case, then the following stsadm command should help you scope your AD lookup the way you want it:
stsadm -o setsiteuseraccountdirectorypath -path <name of OU> -url <URL name>
You could try editing the Distribution List on the Exchange Advanced tab, selecting the "Hide group from Exchange Address lists" check box.
I have not tested this but in theory it would stop the Distribution List from appearing the the list of groups.
Easy fix: add a JavaScript to the page on which those appear that targets and then hides the specific items by applying a CSS style.
I don't have an exact answer, but here's how I would think through the problem. Perhaps you have already answered some of these questions, but it might help to go through them again. I would look at the questions in the following order:
Is there an option in Active Directory to hide a group from SharePoint? (sounds like no)
Is there an option in SharePoint administration (either through stsadm or the actual administration site) to exclude certain users or groups in AD from SharePoint?
Is there a way to configure the web part to exclude certain users or groups from the web part itself?
Is the source code to the web part available such that you can compile the web part to exclude certain groups in the list?
Can you use javascript (as Josh mentioned) in conjunction with the webpart to hide the Distribution Lists from the webpart? (Here's a site with an example of how to use JavaScript to Hide SharePoint's Quick-Launch bar. Maybe that will help).
Those questions are in order from the widest scope and easiest to implement to the narrowest scope that is more difficult to implement. Obviously, you'd like to implement a solution that is easiest to implement, but perhaps you find yourself farther down in the list.
In the last two examples, the solution may appear quite complex, but you may be able to write code that references an XML file of sites to exclude. That way, if your list of Distribution Lists changes, all you have to do is edit the XML file and not edit the source code (of either the javascript or the webpart).
If there's not a simple solution, you'd have to make the painful choice of either 1) letting the problem remain or 2) implementing a hack that adds a dependency to your solution.
I think Distribution Groups that aren't security enabled don't show up in SharePoint. Have you checked AD to see if these groups are security enabled? This may be only for permissions purposes, so I could be wrong.
You will probably need to do a profile import before you see any changes.
You can turn off Distribution Lists entirely, which is what we are doing at my company. This is done by going to the Profile Services Policies in the SSP and disabling the Distribution List feature.
Now if you want to pick and choose the Distribution Lists, it's not that simple, but hopefully this will help someone.

Resources