Investors holding bonds in stock certificate form may approach Receiving Offices for effecting transfer of bonds from one eligible holder to another, through sale or by way of gifts. The Receiving Offices may obtain the Transfer Form (Form III) (See Annex II) duly filled in and witnessed. The Transfer Form may be accompanied by a copy of the Certificate of Holding. The Receiving Office shall cross check the correctness of details given, with the data available on the E-Kuber portal/ their records. The KYC details of both the transferor and transferee may be verified by the Receiving Offices. The transfer request may then be processed through the E-Kuber Portal (for guidance please refer to the User Manual). It may be noted that in terms of sub-section (4) of section 9 of the GS Act, the existing nomination, if any, shall stand cancelled on transfer. If the transferee wants to add a nominee, the Receiving Offices may do the needful as per procedure prescribed at paragraph 5 of these guidelines. A revised Certificate of Holding may be generated from the E-Kuber Portal and issued to the transferee. The transfer of accounts will not disrupt interest payment schedule and the transferee/ holder will continue to earn interest on the relevant due dates.
In case of bonds held as stock certificates, the Receiving office shall input such requests (cancellation/addition) into the E-Kuber system subject to its satisfaction that the details provided are correct and in order, using the facility provided in the E Kuber portal. (For guidance the User Manual may be referred to). Acknowledgement may also be issued.in the prescribed form.
(ii) The pledge/hypothecation/lien on the bond held in stock certificate form shall be recorded and revoked by the banks providing the loan, in accordance with the provisions of section 28 of GS Act and Chapter VII of GS Regulations, using the facility provided in the E-kuber portal (for guidance please see the User Manual available at our website).
The requests of the customer (in plain paper) in case of bonds held in the form of stock certificates, supported by the Certificate of Holding, may be processed by the Receiving Offices through the E-Kuber portal after verification of the particulars and subject to their satisfaction. The Receiving Offices may call for additional documents if deemed necessary. The requests may be entered by Receiving Offices in the RBI portal for giving effect to the changes.
If you have applied for sovereign gold bonds in this issue and you have not received the certificate of holding then you will be shocked to know that your sovereign gold bond certificate is already mailed to you but you are not able to open it.
You just need to open your mail id which you have given at the time of SGB application after that you just need to search ekuber in your email search box, after searching you will get two mails first one will be a funds confirmation receipt and the second one will contain your certificate you just need to download that file and just have to change its extensions to .pdf (just rename and put .pdf at the end of the file name). After doing this you will be able to open the file and it will look like this
Edit 2: Thank you everyone for your help. Within 45 minutes of RBI sending instructions mails to the concerned bank, the bank authorities asked the account number, date of transaction and PAN id. Although I didn't see the message yesterday as it was in my spam folder. Today after noticing their response I sent them all the necessary documents and within 30 minutes they send me the certificate! Edit: I emailed RBI today regarding the issue. Since I was unsure whether my parents' email id was provided or not, and if given which one is as my parents can not tell for sure, I sent a general email only providing the branch name and amount and date. Within an hour RBI sent an email to the concerned bank with me as CC. Let's see what the bank authorities reply. Thank you, everybody, for helping out.
My parents bought SGB from a small finance bank in August. The bank authorities have not provided any received or certificate. I checked the RBI website, where it's mentioned that bank authorities are supposed to give a receipt in the form of a FormB. But my parents haven't received any such! Since then, they've asked the bank when they will get the certificate, which the bank manager keeps saying we will get! The only proof my parents have is their passbook where it is showing a debit corresponding to SGB. Please let me know whether they don't have anything to worry about and how we can get the certificate asap. Thank you.
As the revival in corporate lending, especially the infrastructure segment, gathers steam and the share of such loans goes up, banks are scrambling to manage the shortfall in priority sector lending (PSL) target as a percentage of overall loans by purchasing these certificates.
Banks have the choice of meeting their priority sector lending targets through a mix of lending, buying certificates and contributing to the Rural Infrastructure Development Fund (RIDF). There is a negative return on RIDF contributions; it is 2% below the RBI repo rate. Banks, therefore, prefer to buy PSL certificates despite the high premiums," said a senior banker on condition of anonymity.
He said there is significant demand for certificates backed by core farm loans. In addition, since RBI monitors PSL every quarter, there is more demand at the end of each quarter, especially in March. Depending on the demand, the premiums go up in certain segments. The agricultural portfolio is seasonal, and while there is a loan pickup in the kharif and rabi sowing seasons, the repayments happen during the off-season. Therefore, during off-seasons, the premiums go up," said the banker cited above.
Experts said banks based in south India are primarily net sellers in the PSL certificate market, owing to their sizeable agricultural gold loan portfolio. State-run Central Bank of India is also able to sell a lot of these certificates because of its customer base in Bihar and Uttar Pradesh, where it disburses substantial priority-sector loans.
I am new to GCP/Cloud, and I have created a cluster in GKE and deployed our application there, installed nginx as a pod in the cluster, our company has a authorized SSL certificate which I have uploaded in Certificates in GCP.
In the DNS Service, I have created an A record which matched the IP of Ingress. When I call the URL in the browser, it still shows that the website is still insecure with message "Kubernetes Ingress controller fake certificate".
To ensure all communications between clients and MKE are encrypted, all MKEservices are exposed using HTTPS. By default, this is done usingself-signed TLS certificates that are not trusted by client tools such asweb browsers. Thus, when you try to access MKE, your browser warns that itdoes not trust MKE or that MKE has an invalid certificate.
Mirantis recommends that you make this change outside of peak business hours.Your applications will continue to run normally, but existing MKE clientcertificates will become invalid, and thus users will have to download newcertificates to access MKE from the CLI.
MKE is automatically configured to trust its internal CAs, whichissue client certificates as part of generated client bundles.However, you may supply MKE with additional custom root CAcertificates using this field to enable MKE to trust the clientcertificates issued by your corporate or trusted third-partycertificate authorities. Note that your custom root certificateswill be appended to MKE internal root CA certificates.
After replacing the TLS certificates, your users will not be able toauthenticate with their old client certificate bundles. Ask your usersto access the MKE web UI and download new client certificatebundles.
Finally, Mirantis Secure Registry (MSR) deployments must be reconfigured totrust the new MKE TLS certificates. If you are running MSR 3.0.x, refer to Useyour own TLS certificates.If you are running MSR 2.9.x, refer to Use your own TLS certificates.
Here we add an annotation to set the cert-manager ClusterIssuer to letsencrypt-staging, the test certificate ClusterIssuer created in Step 4. We also add an annotation that describes the type of ingress, in this case nginx.
In the above example, we've used the file provider to handle these definitions.It is the only available method to configure the certificates (as well as the options and the stores).However, in Kubernetes, the certificates can and must be provided by secrets.
With strict SNI checking enabled, Traefik won't allow connections from clients that do not specify a server_name extensionor don't match any of the configured certificates.The default certificate is irrelevant on that matter.
I use some internal services not exposed to the internet. I generate those certificates in my kubernetes cluster using Cert-Manager but then I need to get the out of the cluster to the appropriate applications.
In this blog post, we show you how to set up end-to-end encryption on Amazon Elastic Kubernetes Service (Amazon EKS) with AWS Certificate Manager Private Certificate Authority. For this example of end-to-end encryption, traffic originates from your client and terminates at an Ingress controller server running inside a sample app. By following the instructions in this post, you can set up an NGINX ingress controller on Amazon EKS. As part of the example, we show you how to configure an AWS Network Load Balancer (NLB) with HTTPS using certificates issued via ACM Private CA in front of the ingress controller.
AWS Private CA supports an open source plugin for cert-manager that offers a more secure certificate authority solution for Kubernetes containers. cert-manager is a widely-adopted solution for TLS certificate management in Kubernetes. Customers who use cert-manager for application certificate lifecycle management can now use this solution to improve security over the default cert-manager CA, which stores keys in plaintext in server memory. Customers with regulatory requirements for controlling access to and auditing their CA operations can use this solution to improve auditability and support compliance.
df19127ead